Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

Crispy

send() problem

This topic is 5801 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

What can cause the following thing: once my client has connected to the server, passing its listening port as a message, the server responds by taking the ip from the sockaddr_in struct retrieved from accept(). when calling send() (after socket() and connect()), the server exits without any error messages - the program just closes - bam! this only seems to happen when i send the message to the correct ip address and port - sending it to a non-listening port somewhere only produces the normal SOCKET_ERROR. any ideas why that is so? thanks, crispy

Share this post


Link to post
Share on other sites
Advertisement
programs don''t "just close" unless you hit windows in a particularly painful place.

go to debugger and step through that send() call.

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!