> Unknown exception in the main loop. Aborting... > Possible Cause: No error
This makes me report the following seemingly related sighting that I had today in the middle of something else, w/o exploring it until the end (I did mention it on the IRC earlier today). I've seen a couple of "Failed to open file" messages w/o a file, and decided to hunt for that one. It looks like this is only thrown from within simgear, but always with a path. Closer examination reveals that easyxml.cxx throws it, and uses the same pattern as JSB and I had recently agreed to be problematic --- dynamically creating things on the stack and throwing them! Either I managed to persuade JSB in a wrong C++ fact (I'm not 100% sure about it), or each and every "throw" throughout simgear and flightgear must be reviewed and such usages rewritten. One might argue that this is smth that only aids in error recovery in already screwed up situations, but some exceptions might be thrown to indicate non-globally-fatal situations --- i.e., without looking at every such place we can't be sure. Vassilii _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
