U++ framework
Do not panic. Ask here before giving up.

Home » U++ Library support » U++ MT-multithreading and servers » Lost socket error (and how to get it)
Re: Lost socket error (and how to get it) [message #40208 is a reply to message #40202] Wed, 03 July 2013 08:46 Go to previous messageGo to previous message
koldo is currently offline  koldo
Messages: 3461
Registered: August 2008
Senior Veteran
Hello all

I have not been very clear explaining the problem. Sorry Rolling Eyes

Actual RawConnect() function do not report the real cause of the error. This is due to:
- It just do a SetSockError("connect", -1, "failed");
- As Close() is called every connection try, the error cause is deleted, so no function out of RawConnect() can know it.

A way to improve the function could be to get the source of the problem with GetErrorCode() and TcpSocketErrorDesc() before doing the Close().

In my case I had a buffer overflow error (WSAENOBUFS in Windows). The only way I had to know it was patching the function. Without knowing a problem root cause it is difficult to solve it Very Happy


Best regards
IƱaki
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Need a working simple example of using sockets with GUI in U++
Next Topic: Communicate two PCs using http
Goto Forum:
  


Current Time: Tue Jul 28 10:49:25 GMT+2 2026

Total time taken to generate the page: 0.00757 seconds