Client accidently close when the server crash

[sehang]

The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification

Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it

Writen( sockfd, data.send_buf, strlen( data.send_buf ), __FILE__, __LINE__ );

2. Run TCP Server
3. Run TCP Client (since no writen(), so response from server, it is OK)
4. Close TCP Server
5. A lot of rubbish from TCP Server.........




I also posted the source code here.
Compile TCP Server

gcc -Wall -lmcheck -g -Werror -lpthread -o server server.c

Compile TCP Client

gcc -Wall -lmcheck -g -Werror -lpthread -o client Client.c lib/*.c

I can't upload a zip file, so I upload the source code to the web
http://ericc.member.lostcity-studio.com/SourceCode.zip

[Salem]

Perhaps you could start with the debugger, as in

gdb ./server

When you're ready to run it, just type 'run'

When it crashes, start with the 'bt' command to show the stack trace to the crash location. Identify the most recently called function in your code, and start looking around. Starting with bad pointers.

GDB has a 500+ page manual - it can do a lot of things for you.

[sehang]

Perhaps you could start with the debugger, as in

gdb ./server

When you're ready to run it, just type 'run'

When it crashes, start with the 'bt' command to show the stack trace to the crash location. Identify the most recently called function in your code, and start looking around. Starting with bad pointers.

GDB has a 500+ page manual - it can do a lot of things for you.

Thank you. I try it now.