Question SYSERR: Write to socket: Connection reset by peer

It is not the bug Thomas fixed. It is preceeded with "add_to_lookup failed. Already there. (uid = 15398)". Now if the bug can be triggered.

Without any GDB traceback and info local, this is all speculation.

But is it fixed, If its in the Stock code. We all should get this issue every now Now and Then

You are confusing the issue here. You need to share some GDB output and info local , and a backtrace. There is no idea what is causing your crash. My bug in the stock trigger system has been there for quite a long time.

It happened twice in two days, both backtrace shows this:

Program terminated with signal 6, Aborted.
#0 0x008a6402 in __kernel_vsyscall ()
(gdb) Hangup detected on fd 0
Error detected on fd 0
error detected on stdin

This tells me nothing. I suspect you made code changes and re-compiled. I would suggest you run the game in GDB mode and capture the crashes.

You can do this via "gdb bin/circle" than once inside type run <port#>

than if you have a crash you can capture the backtrace, info local, and any other details.

I didnt make Any change

Im pretty sure this is a Stock problem, that most of you would experience from time to time


My problem is that GDB wont run for very long, Then its run out of momory