> From: Derek Price [mailto:[EMAIL PROTECTED] > > 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?
Probably with some help. Until you see evidence to the contrary always assume I know "windows-NT/*" code reasonably well but the "src/*" code not at all. Questions I have are: What does "buffer" mean in this context? Where do "buffers" come from? Can you translate your question into some specific directions? _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
