Conrad T. Pino wrote: >>From: Conrad T. Pino >> >>http://msdn.microsoft.com/library/en-us/winsock/winsock/select_2.asp >>Beware MS "select" will *NOT* process file handles other than sockets. >>Passing it file or pipe handles will likely fail. I'll verify this. >> >> > >Regrettably very sad but nevertheless it's true. The "WSAGetLastError" >error value is 10038 which is the WSAENOTSOCK symbol. As MSDN says: > >Socket operation on nonsocket. An operation was attempted on something >that is not a socket. > >Either the socket handle parameter did not reference a valid socket, or >for select, a member of an fd_set was not valid. > >
That's exactly what the NO_SOCKET_TO_FD #definition is for and that's why the socket-client.c file is necessary in the first place. Probably someone (likely me) added a call that assumes a socket descriptor may be treated like a file descriptor and neglected to use the #ifdef NO_SOCKET_TO_FD switch to select socket_buffer_initialize instead of fd_buffer_initialize. Can you figure out where the buffer came from? Regards, Derek -- Derek R. Price CVS Solutions Architect Ximbiot <http://ximbiot.com> v: +1 717.579.6168 f: +1 717.234.3125 <mailto:[EMAIL PROTECTED]> _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
