Problem:
- Call to send(), returns Winsock Error 10038 against socket handle
Illustration:
acceptedSocket = accept (server, (sockaddr *)&sin, &len);
- accept(), returns 0
- A new thread, is created for each connection
- send(), (in thread function) returns 10038
Illustration: — in thread function
//omitted
SOCKET RemoteSocket = (SOCKET) client;
//omitted
send (RemoteSocket, stringToSpend, strlen(stringToSpend), 0)
Suggestions:
- Possible, race condition?
- Could use I/O completion ports, but not at this stage
asked Feb 23, 2009 at 14:23
AaronAaron
2,8139 gold badges44 silver badges57 bronze badges
Isn’t the problem in the line
acceptedSocket = accept (server, (sockaddr *)&sin, &len) == INVALID_SOCKET)
You make acceptedSocket the result of the comparison, but you should store the actual socket returned from accept somehow:
acceptedSocket = accept (server, (sockaddr *)&sin, &len);
isOK= acceptedSocket!=INVALID_SOCKET;
Although I’m a bit confused by the unbalanced parentheses in your post, so I may be wrong
answered Feb 23, 2009 at 14:52
jpalecekjpalecek
46.7k7 gold badges102 silver badges140 bronze badges
0
accept() returns you a handle to a new connection-specific socket. for server code it’s 2+ sockets involved: one is in listen state you are calling accept() for and second is one returned from accept() — it’s an incoming connection socket. Following accept() can return socket for second incoming connection etc. if accept() returns 0 it’s not an incoming connection — it’s an error.
answered Feb 23, 2009 at 14:43
grigoryvpgrigoryvp
40k63 gold badges173 silver badges276 bronze badges
1
Hmm, seems like your send is executing too fast before the accept happened. So the socket used in send is not valid at the point send is executed. One of the obnoxious feature of multithreading. You need to wait for an event at the send thread and fire an event when an accept occurs
answered Feb 23, 2009 at 14:50
rptonyrptony
1,0241 gold badge12 silver badges22 bronze badges
1
| description | ms.assetid | title | ms.topic | ms.date |
|---|---|---|---|---|
|
Windows Sockets (Winsock) error codes returned by the WSAGetLastError function. |
50b924f3-2c88-443b-8a90-4293fe5c3048 |
Windows Sockets Error Codes (Winsock2.h) |
reference |
05/31/2018 |
Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic.
The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description associated with an error code are defined in the Winerror.h header file. The FormatMessage function can be used to obtain the message string for the returned error.
For information on how to handle error codes when porting socket applications to Winsock, see Error Codes — errno, h_errno and WSAGetLastError.
The following list describes the possible error codes returned by the WSAGetLastError function. Errors are listed in numerical order with the error macro name. Some error codes defined in the Winsock2.h header file are not returned from any function.
| Return code/value | Description |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
Overlapped operations will complete later.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Requirements
| Requirement | Value |
|---|---|
| Header |
|
See also
-
Error Codes — errno, h_errno and WSAGetLastError
-
Handling Winsock Errors
-
FormatMessage
-
WSAGetLastError
Speed up your PC in just a few clicks
Download this software now and say goodbye to your computer problems.
If you have Winsock Accept 10038 on your computer, this blog post will help you fix it. Scarcity is usually associated with adequate resources or RAM If the computer’s memory is full, a Winsock Full error will occur when the preparer tries to connect to the Internet or another computer. This can be solved by restarting your computer, turning it off and then back on again. Minor bugs related to clogging of RAM have been fixed in this car.
Hope you havehave a nice day. One more problem with the exit, one more day 🙂
I finally installed MicroSoft Visual (MSVC ++) c ++ IDE as well as Platform SDK in order to be able to compile Winsock applications.
What is WSAConnect?
The WSAConnect function is called to connect to the actual specified destination and to perform a number of other ancillary operations, most often during the connection. When socket s is not tied, the system assigns unique aspects to the local organization and marks the socket as tied.
We missed a lot here. In the ServerSocket :: accept () function, it creates a new circumstance from the ClientSocket and sets its plugin file descriptor to the one from which accept () was created when good.My was running
Speed up your PC in just a few clicks
Is your computer running slow and unstable? Are you plagued by mysterious errors, and worried about data loss or hardware failure? Then you need ASR Pro � the ultimate software for repairing Windows problems. With ASR Pro, you can fix a wide range of issues in just a few clicks, including the dreaded Blue Screen of Death. The application also detects crashing applications and files, so you can quickly resolve their problems. And best of all, it�s completely free! So don�t wait � download ASR Pro now and enjoy a smooth, stable and error-free PC experience.
in the ClientSocket :: recv () function, I (obviously) call the recv () function from this Winsock library over the phone. The problem I am facing is that the output descriptor I was using was recognized by recv () as invalid, but only one server side client socket returned by my ServerSocket :: accept () is the client side instance instance customer has no problem. I’ve included a few statements to debug that the handle is valid.
The weirdest information about this is that when I put the exact same code with MinGW gcc / g ++ on Windows, it works perfect! The above problem only occurs when using MSVC ++.
string ClientSocket ::recv (int bufsize) { if (! isConnected ()) throw SocketException ("Not connected."); cout << "SocketRecv:" << (sockfd == INVALID_SOCKET) << "" << sockfd << endl; vector buffer (buffer size + 1, 0); cout << "SocketRecv1:" << (sockfd == INVALID_SOCKET) << "" << sockfd << endl; int ret matches :: recv (sockfd, & buffer [0], bufsize, 0); cout << "SocketRecv2: width in inches << (sockfd == INVALID_SOCKET) << inches" << sockfd << endl; // ret is obviously -1 due to an "invalid" plugin descriptor, but // Beyond statements return null (false) relative to (sockfd == INVALID_SOCKET) -: n if (ret <0) # ifdef_WIN32 switch ((ret = WSAGetLastError ())) #another Switch (error) #end if case DECONNREFUSED: // The 'd' prefix can mean that _I_ defined it, i.e. screens in question // set to 'WSAECONNREFUSED' but Linux always sets to 'ECONNREFUSED' throw SocketException ("Connection lost while recovering."); Pause; DENOTCONN event: throw SocketException ("Not connected."); Pause; The DECONNABORTE Case: SocketException ("The launch of the program helped to terminate the connection."); Pause; DECONNRESET script: throw SocketException ("Reset peer connection."); Pause;Initially: // usually itoa (), and char / string characters are not suitable ... I needed this in // to see what the problem is. Character-tmp [21]; string = tmp4 "Unknown socket error."; Guitar string tmp3 = tmp4 + tmp, itoa (ret, 10); // This rejection keeps on throwing "Unknown error while reading from socket. 10038" SocketException thrown (tmp3); Pause; also if (ret == 0) connected = false; resume ""; return & buffer [0];
What is WSACleanup?
WSACleanup () decrements the counter and frees most of the DLL as soon as the counter reaches 2. Typically, you should call WSAStartup () in your application’s initialization function or WSACleanup () just before exiting the main application.
Additional information: The socket is in blocking mode, that is, it has not been configured to non-blocking. I have successfully called WSAStartup (). This happens on the server factor, on the ClientSocket, the instance is returned by my ServerSocket :: accept () (yes, I checked that handle as well — really good). Instances of «WSAECONNRESET (10054)» or «WSAECONNABORTED (10053)» on the client side.
I can’t think of anything else that would be an intuitive sensation. To make matters worse, it performs better with MinGW gcc / g ++ than Windows and Linux.
How to solve socket error 10038?
Problem. The user is authenticated with the Citrix Storefront cloud controller.Symptom. Citrix receiver.The root cause.To solve the problem.
If you want to see the whole library, it is always inserted in: (Warning: lines!) 600+
Socket.cxx> http://paste.pocoo.org/ show / 353725 /
Socket.hxx — http://paste.pocoo.org/show/353726/
Update. As Ben’s solution, I’m currently using: void ServerSocket :: accept (ClientSocket & sock); then I implement as: ClientSocket mysock; Server.
accept (mysock);
Download this software now and say goodbye to your computer problems.
Winsock Accetta 10038
Winsock Accepteren 10038
Winsock Accepter 10038
Winsock Aceptar 10038
Winsock Acceptera 10038
Winsock 수락 10038
Winsock Zaakceptuj 10038
Winsock Akzeptieren 10038
Winsock Aceita 10038
Winsock Prinimaet 10038
THE INFORMATION IN THIS ARTICLE APPLIES TO:
- All Windows-based products
DISCUSSION
The table below lists some common Winsock error codes. Also refer to the Microsoft MSDN Library article «Winsock Error Codes» at http://msdn.microsoft.com/en-us/library/aa924071.aspx.
| Return Code | Value | Description |
|---|---|---|
| WSAEINTR | 10004 | Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall. |
| WSAEACCES | 10013 |
Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option. |
| WSAEFAULT | 10014 |
Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr). |
| WSAEINVAL | 10022 |
Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening. |
| WSAEMFILE | 10024 |
Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread. |
| WSAEWOULDBLOCK | 10035 |
Resource temporarily unavailable. This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established. |
| WSAEINPROGRESS | 10036 |
Operation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error. |
| WSAEALREADY | 10037 |
Operation already in progress. An operation was attempted on a non-blocking socket with an operation already in progress—that is, calling connect a second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed. |
| WSAENOTSOCK | 10038 | Socket operation on nonsocket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid. |
| WSAEDESTADDRREQ | 10039 |
Destination address required. A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY. |
| WSAEMSGSIZE | 10040 |
Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself. |
| WSAEPROTOTYPE | 10041 |
Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM. |
| WSAENOPROTOOPT | 10042 |
Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call. |
| WSAEPROTONOSUPPORT | 10043 |
Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol. |
| WSAESOCKTNOSUPPORT | 10044 |
Socket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all. |
| WSAEOPNOTSUPP | 10045 |
Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket. |
| WSAEPFNOSUPPORT | 10046 |
Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT. |
| WSAEAFNOSUPPORT | 10047 |
Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto. |
| WSAEADDRINUSE | 10048 |
Address already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all— connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf. |
| WSAEADDRNOTAVAIL | 10049 |
Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0). |
| WSAENETDOWN | 10050 |
Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself. |
| WSAENETUNREACH | 10051 |
Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. |
| WSAENETRESET | 10052 |
Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed. |
| WSAECONNABORTED | 10053 |
Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error. |
| WSAECONNRESET | 10054 |
Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET. For more information see GlobalSCAPE Knowledge Base Article #10235 |
| WSAENOBUFS | 10055 |
No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. This error indicates a shortage of resources on your system. It can occur if you’re trying to run too many applications (of any kind) simultaneously on your machine. If this tends to occur after running certain applications for a while, it might be a symptom of an application that doesn’t return system resources (like memory) properly. It may also indicate you are not closing the applications properly. If it persists, exit Windows or reboot your machine to remedy the problem. Another possible solution is to increase the available virtual memory by increasing the size of the Windows paging file. For more information see GlobalSCAPE Knowledge Base Article |
| WSAEISCONN | 10056 |
Socket is already connected. A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence. |
| WSAENOTCONN | 10057 |
Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset. |
| WSAESHUTDOWN | 10058 |
Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued. |
| WSAETIMEDOUT | 10060 |
Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond. For more information see GlobalSCAPE Knowledge Base Article |
| WSAECONNREFUSED | 10061 |
Connection refused. |
| WSAEHOSTDOWN | 10064 |
Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT. |
| WSAEHOSTUNREACH | 10065 |
No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH. |
| WSAEPROCLIM | 10067 |
Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously.WSAStartup may fail with this error if the limit has been reached. |
| WSASYSNOTREADY | 10091 | Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check:
|
| WSAVERNOTSUPPORTED | 192 | Winsock.dll version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed. |
| WSANOTINITIALISED | 10093 | Successful WSAStartup not yet performed. Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times. |
| WSAEDISCON | 10101 |
Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence. |
| WSATYPE_NOT_FOUND | 10109 |
Class type not found. The specified class was not found. |
| WSAHOST_NOT_FOUND | 11001 |
Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database. |
| WSATRY_AGAIN | 11002 | Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. |
| WSANO_RECOVERY | 11003 | This is a nonrecoverable error. This indicates that some sort of non-recoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error. |
| WSANO_DATA | 11004 |
Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. |
| WSA_INVALID_HANDLE | OS Dependent |
Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid. |
| WSA_INVALID_PARAMETER | OS Dependent |
One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters. |
| WSA_IO_INCOMPLETE | OS Dependent |
Overlapped I/O event object not in signaled state. The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete. |
| WSA_IO_PENDING | OS Dependent | Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed. |
| WSA_NOT_ENOUGH_MEMORY | OS Dependent |
Insufficient memory available. An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources. |
| WSA_OPERATION_ABORTED | OS Dependent |
Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl. |
| WSAINVALIDPROCTABLE | OS Dependent |
Invalid procedure table from service provider. A service provider returned a bogus procedure table to Ws2_32.dll. (This is usually caused by one or more of the function pointers being null.) |
| WSAINVALIDPROVIDER | OS Dependent |
Invalid service provider version number. A service provider returned a version number other than 2.0. |
| WSAPROVIDERFAILEDINIT | OS Dependent |
Unable to initialize a service provider. Either a service provider’s DLL could not be loaded (LoadLibrary failed) or the provider’s WSPStartup/NSPStartup function failed. |
| WSASYSCALLFAILURE | OS Dependent |
System call failure. Generic error code, returned under various conditions. Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs. Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error. |
«Отладка и поиск неисправностей», «Список ошибок MyChat Client», «Сетевые ошибки», «#10038: socket operation on nonsocket».
Ошибка
Сетевая ошибка 10038: «Socket operation on nonsocket»
Описание ошибки
•Вы пытаетесь работать с неоткрытым или уже закрытым сетевым сокетом.
•Вы указываете неправильный или несуществующий адрес для bind серверного сокета.
•Вы пытаетесь сделать bind IPv6 локального адреса для сокета, который работает на IPv4 или наоборот.
Решение проблемы
Проверьте корректность адреса серверного сокета для bind и его физическую доступность.
|
|
|
|
Правила раздела Visual C++ / MFC / WTL (далее Раздела)
Winsock2 -ошибка 10038
, select с не-сокетом
- Подписаться на тему
- Сообщить другу
- Скачать/распечатать тему
|
|
|
|
бухантер
Рейтинг (т): 120 |
Привет всем. Решил подтвердить свою чёрную догадку — проверил на валидность сокета. Действительно — сокет стал инвалидом. И кто это его подрихтовал? Только что живой был, accept-ился нормально, даже в логах запись осталась — вот такой то сокет, принят тогда то, … , и вдруг :tank: Я бы не очень рассраивался, если бы это произошло 1 раз. Дык происходит каждый (приблизительно) пятый раз. Есть ли у кого нибудь идеи, как защитить моего зверька-сокета от вредных дядей? (хм, возможно, дяди пришли из других процессов, а откуда ещё? — я то ведь closesocket не говорил?!). Спасибо за внимание. |
|
Ace |
|
|
AQL, а не ты тот самый вредный дядя? Красочное описание канечна хорошо, ты кодом делись…. |
|
UncleBob |
|
|
А то что ты подпихиваешь в fd_set, похоже на хэндл сокета или нет? |
|
Бобёр |
|
|
бухантер
Рейтинг (т): 120 |
Всё похоже и всё работает. В 80% случаях. Сообщение отредактировано: AQL — 24.05.04, 09:11 |
|
Muran |
|
|
а может кто-то на другой стороне закрыл соединение.. сокет опятьже станет инвалидным т.к. пришло сообщение FD_CLOSE от другой стороны.. то, что ты его не закрывал вручную ещё ни о чем не говорит.. |
|
UncleBob |
|
|
Цитата Muran, 24.05.04, 17:40 хэндл сокета в этом случае должен жить |
0 пользователей читают эту тему (0 гостей и 0 скрытых пользователей)
0 пользователей:
- Предыдущая тема
- Visual C++ / MFC / WTL
- Следующая тема
[ Script execution time: 0,0523 ] [ 16 queries used ] [ Generated: 7.06.23, 05:56 GMT ]