delorie.com/archives/browse.cgi | search |
On Thu, Nov 15, 2001 at 05:14:55PM -0500, Jonathan Kamens wrote: > > Date: Thu, 15 Nov 2001 23:06:25 +0100 > > From: Corinna Vinschen <vinschen AT redhat DOT com> > > > > Don't think so. I think we could find a workaround by assigning > > local socket numbers in another range (>32768 or so). > > This will not solve the problem. > > If you read my test program, you will see that I am calling bind() on > the socket before connect(), and the bind() succeeds *** even though > the connect subsequently fails with WSAEADDRINUSE ***. So there's no > way to detect that winsock has assigned an in-use port to the socket > until it's too late. Can you give me a pointer to the KB article describing that winsock bug? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |