This is the mail archive of the
mailing list for the Cygwin project.
Re: select() implementation question
On Tue, Jun 20, 2000 at 01:10:48AM +0200, Boris Schäling wrote:
>> -----Original Message-----
>> From: firstname.lastname@example.org
>> [mailto:email@example.com]On Behalf Of Chris Faylor
>> Sent: Monday, June 19, 2000 8:34 PM
>> To: firstname.lastname@example.org
>> Subject: Re: select() implementation question
>> select() on a socket uses the winsock version of select it does not
>> establish connections, AFAIK.
>I've written a small C program: It initializes a struct sockaddr_in, calls
>socket(), bind(), listen() and saves the socket in a fd_set. Now there is
>exact one listening port. Then select() is called (and the fd_set is passed
>to select()). A second random port is opened for listening. When select()
>returns "something" connects to this second random port and a connection is
>established. After that this listening port is closed but the connection
>I have no problems to use "my" listening port - everything works well. I
>just noticed that there are some additional unusual things happening so I
>want to make sure that this is cygwin and not a bug in my application. Can
>anyone confirm this behaviour of network applications under cygwin? If you
>like I can send you the C source code: one file, 50 lines, nothing special.
>It would be nice to know that this is select()'s standard behaviour then I
>could happily go on coding.
I can only repeat what I said above. Cygwin is working with all sorts of
networking applications currently but that doesn't mean that there is
not a problem lurking somewhere. The source code is available if you want
to debug it but, I'm sorry, this is not something that I will be able
to track down.
Taking a quick glance at select.cc, I can see that cygwin select does
open a dummy socket. Possibly it is not closing something when it
returns. I really don't know.
Want to unsubscribe from this list?
Send a message to email@example.com