old bug with thread sending score, linux
|Opened on:||Sunday, January 18, 2015 - 13:26|
|Last modified:||Sunday, January 18, 2015 - 13:26|
On all puzzles, only on Linux
Running fast functions that don't create new threads (cut, setRotamer...) there is a thread that crashes:
Program received signal SIGPIPE, Broken pipe.
0x00002aaaab7c92dd in write () at ../sysdeps/unix/syscall-template.S:81
Running with gdb it still run for days, but not on normal mode. That thread is the one that updates the score and send it to the server.