This is the mail archive of the
mailing list for the Cygwin project.
RE: select() implementation question
- To: <cygwin at sourceware dot cygnus dot com>
- Subject: RE: select() implementation question
- From: Boris Schäling <boriss at web dot de>
- Date: Tue, 20 Jun 2000 16:31:41 +0200
> -----Original Message-----
> From: email@example.com
> [mailto:firstname.lastname@example.org]On Behalf Of Chris Faylor
> Sent: Tuesday, June 20, 2000 2:12 AM
> To: email@example.com
> Subject: Re: select() implementation question
> 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.
Ah, a dummy socket. Well, then I think this is not a bug but a feature: I
guess this socket is used to jump back from select() whenever cygwin needs
to do so. There are probably some things to do that can't wait until a
socket is ready or the timer decreased to 0. I think this additional socket
is used to have some sort of control and to interrupt select() in a proper
However, I downloaded the source code of select(). I'll have a look when I
have some time.
BTW: Is anybody working already on an implementation of getaddrinfo(),
gai_strerror() and freeaddrinfo()? Otherwise I will try. :-)
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org