Re: problem/bug in select command of socket / winsock

[Christopher Faylor <cgf at redhat dot com>]

On Wed, Jul 25, 2001 at 12:31:08PM -0700, haase@msg.ucsf.edu wrote:
>Hi,
>I wrote a C++ / wxWindows (very nice GUI lib :-) program.
>It normally handles TCP/IP socket communication by utilizing it's
>"event-handling" system - so that e.g.  recv() doesn't block the program
>until data arrives  -- all that works fine.
>
>But I have a extra / second thread dedicated just to read from a socket .
>This _HAS_ to block on recv - otherwise it would run in circles and use up
>100% CPU while waiting on data. This mode in wxWindows is activated with:
>socket->SetFlag(wxSOCKET_BLOCK).  I found that that is implemented by
>using a ("blocking") select()  [somewhere inside a part that wxWindows
>calls their GSocket implementation]
>
>So: all this works fine when I compile on VC++ (6)
>    But cygwin just seems to run right through the select() call  [ I used
>the gdb -- very fancy :-)) someone did a good job!! ]
>
>
>I read that there is an issue about if or how to use the winsock part or
>the posix-compliant cygwin version  .   Is that a way to influence that
>or did I just found a bug?

You really haven't provided enough details to tell if this is a bug
or not.

AFAIK, there aren't any issues with select on sockets.  If there were then
things like inetd or ssh would be inoperable.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/