Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <39F8595A.B37B03F4@ece.gatech.edu>
Date: Thu, 26 Oct 2000 12:18:34 -0400
From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: Mark Swanson <Mark.Swanson@techspan.com>
CC: cygwin@sources.redhat.com
Subject: Re: Bug report: with CVS
References: <20001023142004.17298.qmail@web122.yahoomail.com> <39F454C8.14003F89@techspan.com> <39F71352.5847F251@ece.gatech.edu> <39F75794.5185485D@techspan.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Mark Swanson wrote:
> 
> Here's some additional info: perhaps you can make sense of the strace
> output?
> 

Well, the strace output didn't seem any more informative to me that the
original error message.  But, Corinna just checked in a fix that may
affect this problem -- why don't you try tonight's snapshot of
cygwin1.dll...

> For some reason there are systems (mostly 9x/ME, seldom NT) which flawed
> to duplicate a socket so that the duplicated socket isn't usable in
> further socket function calls. All those functions will then return
> WSAENOTSOCK.

"seldom NT" -- but not "never".  Perhaps this is the problem on your
machine...

> Anyway, the good news is, there's a way to work around that flaw.
> I'm now using special Winsock2 functions (WSADuplicateSocket/WSASocket)
> to duplicate the socket to the child process which is the recommended
> way for sharing sockets on Windows platforms.
[snip]
> Ok, I have just checked in the patch so it's accessible via CVS
> already or it will be in the next developers snapshot.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com