On Tue, Sep 9, 2008 at 5:03 AM, Chris Ahrendt celticht32@aol.com wrote:
I started narrowing down some information in debugging a winemm issue and noticed the following in my logs...
trace:winsock:WSARecvFrom socket 00e8, wsabuf 0x33f638, nbufs 1, flags 0, from 0x33f67c, fromlen 16, ovl (nil), func (nil) trace:winsock:WSARecvFrom fd=51, options=0 warn:winsock:WSARecvFrom -> ERROR 10035
The 10035 is a buffer overflow error (I think)
No, 10035 is WSAEWOULDBLOCK, which is normal for WSARecvFrom() on non-blocking sockets that currently have no data in the receive buffer.
and I don't know much if at all how this set of code is supposed to work... anyone else getting this with the latest git tree?
and any help on figuring out why the buffer is getting this error...
I'd be more worried if it wasn't :-).
thanks
Chris
Bye Damjan