socket errors...

[James Hawkins]

On Mon, Sep 8, 2008 at 10:03 PM, Chris Ahrendt <celticht32 at 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)
>
> 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...
>

A little context might help...I, for one, have no idea what you're
talking about.

-- 
James Hawkins