- assigned issue to
- changed status to open
Server initialization failure causes program crash
When the Cafu server fails to initialize (e.g. when it could not obtain a socket on server port) and subsequently [http://trac.cafu.de/browser/cafu/trunk/Ca3DE/Server/Server.cpp?rev=174#L164 throws an exception] (or for that matter, any other initialization code throws an exception that goes unhandled in Cafu code), the exception propagates through wxWidgets code and eventually causes program termination.
Unfortunately, wxWidgets catches such exceptions and re-throws them, making it impossible to see in the stack trace where the exception originated. Enabling C++ EH exceptions in the Event Filter dialog of WinDbg makes it possible to catch the exception first chance, though.
See - http://www.cafu.de/forum/viewtopic.php?f=6&t=808 for details and the original report, - http://docs.wxwidgets.org/trunk/overview_exceptions.html for additional information.
Comments (3)
-
reporter -
reporter - changed status to resolved
(In [179]) Cafu: Improved handling of errors that occur during program initialization. Closes
#53. -
reporter - removed version
Removing version: svn-head (automated comment)
- Log in to comment
Under Linux and Windows 2000, this can be reproduced by running the Cafu executable like
(under 64-bit Win7, using 32-bit Cafu, I was not able to reproduce this, i.e. it succeeded no matter the server port number).
Also see - http://thread.gmane.org/gmane.comp.lib.wxwidgets.general/71406