Unknown server bug causing crashes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Game>Connect to Server
2. Select alderan.cz and click connect

What is the expected output? What do you see instead?
Game>Create Game or Game>Join Game should be avaliable but Game>Create Game
and Game>Join Game are both grayed out and Game>Disconnect is also greyed out.

What version of the product are you using? On what operating system?
I see the problem with both 0.1.3 and R144 on Windows (XP and Vista).

Please provide any additional information below.
I had been playing a few matches before everyone disconnected and when I
tried to reconnect to the server I ran into this problem.

Original issue reported on code.google.com by npburg2...@gmail.com on 20 Jun 2009 at 6:59

[GoogleCodeExporter]

Thank you for report. The server is now on again.
There was a crash today early in the morning - 2009-06-20 some time after 04:45 
CET.
The crash was caused by a bug in the server, but I'm not sure where exactly the 
bug
was. I need a report of players that was playing and probably caused the server 
to
fall. From the log I know that there where these people on the server:
 * iT
 * Kurt
 * yap~
 * PTT QQ
 * Blankster
 * vacakk
 * CONPANSATE
 * Ken
If you're one of these and remember what preceded to that server crash, please 
enter
your report.

The following information is for developers. The server ends up with this debug 
message:
Removing player #2.
"Client (375): onActionRequest(1)"
"Client (375): onActionRequest(1)"
Removing player #5.
Removing player #4.
[CLIENT]   onActionPlayCard
"VoidAI (3732): onActionRequest(2)"
"VoidAI (3732): REQUEST_RESPOND"
Trying to play:  "bang"
"Client (375): onActionRequest(1)"
Removing player #1.
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'BadGameStateException'

Original comment by MacJar...@gmail.com on 20 Jun 2009 at 1:07

• Changed title: Unknown server bug causing crashes
• Changed state: Accepted
• Added labels: Component-Server, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This issue was fixed by r166. Similar server crash (broken-pipe signal received 
on
server) was fixed by r171.

Original comment by MacJar...@gmail.com on 4 Jul 2009 at 5:19

• Changed state: Fixed

[GoogleCodeExporter]

Server "crashed" again on SIGPIPE (broken-pipe signal). I've just find out that 
it's
not actually a crash and that it's caused by gdb. Gdb by default pauses the 
process
when SIGPIPE is received. If you don't use gdb, SIGPIPE should be simple 
ignored.

The starting script on alderan.cz is now modified that gdb should not pause the
process on SIGPIPE.

Original comment by MacJar...@gmail.com on 7 Jul 2009 at 6:21