SDLNet - Disconnect on Recv(...);?

Ryan Fleury · 2012-06-06T22:17:29

I'm aware I just made a post about SDL_net; however, I have run into a new problem. Packets are sending and getting received. However, when the server receives the data, the client simply disconnects. The SDLNet_TCP_Recv(...); function returns -1. I cannot find the error, for SDLNet_GetError(); isn't working for me(it returns nothing). Has anybody run into this problem before? My code is below. //Receiving Code result = SDLNet_CheckSockets(player_sockSet, 0); //loop through each client for(int client = 0; client < maxPlayers; client++) { //check the socket for activity int clientSocketActivity = SDLNet_SocketReady(players[client].sock); if(players[client].connected == true && clientSocketActivity > 0) { //attempt to read from the socket. //non-positive return values indicate error int bytesRecv = SDLNet_TCP_Recv(players[client].sock, msg, 256); if(bytesRecv > 0) { //display the result stringstream ss; ss << "Received " << bytesRecv << " bytes from client " << client << "!"; consoleOut(ss.str()); } else { //there was an error stringstream ss; ss << "Player " << client << " has disconnected."; consoleOut(ss.str()); players[client].connected = false; connectedPlayers--; //disconnect the socket } } } Please excuse the bad indenting, it's because of copy + paste. Thanks in advance! -Ex

Networking and Multiplayer Programming

Started by Exiled June 06, 2012 03:57 AM

10 comments, last by hplus0603 11 years, 10 months ago

Exiled

105

Author

June 06, 2012 08:07 PM

As I said before. You do not analysed the traffic.

This only makes it a better guess.
Between you clients and the server you have the TCP/IP stacks of two machines and the wireing between them. Or if they run on one machine you even have the TCP/IP stack between the two application and the operating system anyways.
If you have a hardware with multiple cores running you have parallel execution of the two applications. That a lot of stuff. And as long as you do not check the traffic between your clients and the server you are only guessing.

You are seeing misbehaviour and you do not have a clue whats wrong. So you worry about whats wrong but you must prove your result. This is how failure analysis is done. And while developing software you will do this all the time. If you are not proving your idea about the failure you cannot exclude things.

What you are doing right now is excluding without knowledge. This is fatal and not best practice.

"I do not analysed the traffic"....

You have no direct point, Telnet is developed by Microsoft. Both my client and Telnet disconnect when the server receives something. This means the fault is with the server; it cannot be with the client.

hplus0603

11,916

June 06, 2012 10:17 PM

You need to bring up the server in a debugger. Put a breakpoint where it receives the data. Look at what it does -- step through each line, until you get to a point where the server either closes the socket, or exits the process. Congratulations! You have now found the point where the server drops the client!

enum Bool { True, False, FileNotFound };

SDLNet - Disconnect on Recv(...);?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

SDLNet - Disconnect on Recv(...);?

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines