Re: WSAENOBUFS on winsock client application
- From: FriedhelmEichin <FriedhelmEichin@xxxxxxxxxxxxxxxx>
- Date: Fri, 9 May 2008 02:13:01 -0700
The application is running on Windows XP SP2.
The error code is returned if a preceeding connection has been broken caused
by network issues and a new connection attempt is made within the thread. But
this is not deterministic, normally the following connection attempt
succeeds. It may happen after a few disconnects after minutes or even days...
--
best regards
friedhelm
"Volodymyr M. Shcherbyna" wrote:
I analyzed winsock sources (XP SP2), and the error WSAENOBUFS is returned
usually when allocation of memory failes (RtlHeapAllocate(...)) or
equivalents:
What is your OS?
--
V.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"FriedhelmEichin" <FriedhelmEichin@xxxxxxxxxxxxxxxx> wrote in message
news:FB4F7278-628C-4AF1-A22A-278509CE667B@xxxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: WSAENOBUFS on winsock client application
- From: Volodymyr M. Shcherbyna
- Re: WSAENOBUFS on winsock client application
- References:
- WSAENOBUFS on winsock client application
- From: FriedhelmEichin
- Re: WSAENOBUFS on winsock client application
- From: Volodymyr M. Shcherbyna
- WSAENOBUFS on winsock client application
- Prev by Date: Re: WSAENOBUFS on winsock client application
- Next by Date: Re: WSAENOBUFS on winsock client application
- Previous by thread: Re: WSAENOBUFS on winsock client application
- Next by thread: Re: WSAENOBUFS on winsock client application
- Index(es):
Relevant Pages
|
|