Actually that wasn't a crash backtrace, it was a SIGPIPE backtrace -- when debugging a networking application, you often get SIGPIPE's, which doesn't indicate a real error. You need to continue debugging to get to the real crash backtrace.
Since the bug is rather old, do you still see this problem at all?
Actually that wasn't a crash backtrace, it was a SIGPIPE backtrace -- when debugging a networking application, you often get SIGPIPE's, which doesn't indicate a real error. You need to continue debugging to get to the real crash backtrace.
Since the bug is rather old, do you still see this problem at all?