[PATCH] Handle case where an AI sends an invalid message and then crashes
authorSam Moore <matches@ucc.asn.au>
Sat, 5 May 2012 13:03:33 +0000 (21:03 +0800)
committerSam Moore <matches@ucc.asn.au>
Sat, 5 May 2012 13:03:33 +0000 (21:03 +0800)
commitadd28d0a7f265f5fcfdd67a4c1e590b19f76272e
tree1902dc4bb30a8654b1ed3ae510ab19027c2b2079
parentde2ad1b17a94aceb8527b3b6a34c7a1732fcd4cf
[PATCH] Handle case where an AI sends an invalid message and then crashes

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]
judge/manager/ai_controller.cpp
judge/manager/ai_controller.h
judge/manager/controller.cpp
judge/manager/controller.h
judge/manager/game.cpp
judge/manager/game.h
judge/manager/human_controller.h
judge/manager/main.cpp
judge/manager/network_controller.h
judge/manager/program.cpp

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