"Stephan Jaschke" <news@stj-software.de> wrote in message
news:4602e6e7@newsgroups.borland.com...
> Send must have returned Id_SOCKET_ERROR (SOCKET_ERROR)
> and WSAGetLastError returns 0. But I see no explanaition for this
> situation in the SDK docs.
Obviously, that is not the place where the exception is actually
occuring. IOHandler.Send() ultimately calls the Win32 API send()
function, and then returns the original result. send() is guaranteed
to call WSASetLastError() with a meaningful error if SOCKET_ERROR is
returned. So the exception has to be occuring somewhere else. Your
call stack is incomplete. TIdTCPConnection.WriteBuffer() does not
directly call TIdStack.RaiseSocketError(). There where is all of the
calls in between for either TIdStack.CheckForSocketError() or
TIdStack.RaiseSocketError()?
Gambit
