[PATCH] Handle case where an AI sends an invalid message and then crashes
authorSam Moore <[email protected]>
Sat, 5 May 2012 13:03:33 +0000 (21:03 +0800)
committerSam Moore <[email protected]>
Sat, 5 May 2012 13:03:33 +0000 (21:03 +0800)
If an AI sent a bad move and then crashed, a SIGPIPE would be reported
rather than the AI's bad move.

NOTE: There is an issue with Program::Running, because the segfaulted AI
still returns 'true', which leads to confusion in handling SIGPIPE.

Should probably handle segfaulting AIs better.
Then again, people should probably not make segfaulting AIs.

[SZM]


No differences found

UCC git Repository :: git.ucc.asn.au