[firstname.lastname@example.org: Re: ENOTSOCK errors with cygwin dll 1.3.21 and 1.3.22]
Wed May 28 19:40:00 GMT 2003
On Wed, May 28, 2003 at 09:54:39AM -0400, Pierre A. Humblet wrote:
> Corinna Vinschen wrote:
> > On Wed, May 28, 2003 at 09:14:52AM -0400, Pierre A. Humblet wrote:
> > > Another test, more direct, would be to point prot_info_ptr to a dynamic
> > > (on the stack) WSAPROTOCOL_INFOA structure during the dup operation,
> > > and to restore it to point to the cygheap area at the end of the dup.
> > > If it works, we know the problem is somehow related to the cygheap
> > > and we can start looking it it.
> > Nope. No change.
> > Corinna
> Sorry to ask, just in case: you changed the prot_info_ptr of the child,
> not the one of the parent?
What parent/child relationship are you talking about? I'm still using
Jason's application for testing which creates a socket, switches user
context, dup's and the closes the dup'd socket. The problem happens
in dup() which doesn't involve any second process. Btw., on *my* box
the problem happens in *both* cases, started from cmd as well as from
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.
More information about the Cygwin-developers