Changeset 7175

Timestamp:

Aug 18, 2010, 12:12:42 AM (14 years ago)

Author:

rgrieder

Message:

Fixed a problem with Ogre 1.7 and our exception handling mechanism. Somehow Ogre exceptions don't like if you completely reload Ogre during throw and catch…
The fix is simple: Abort the program if graphics loading fails (but display the exception message).

File:

• code/trunk/src/libraries/core/Core.cc (modified) (1 diff)

code/trunk/src/libraries/core/Core.cc

@@ -229 +229 @@
 
         // Upgrade OGRE to receive a render window
-        graphicsManager_->upgradeToGraphics();
+        try
+        {
+            graphicsManager_->upgradeToGraphics();
+        }
+        catch (...)
+        {
+            // Recovery from this is very difficult. It requires to completely
+            // destroy Ogre related objects and load again (without graphics).
+            // However since Ogre 1.7 there seems to be a problem when Ogre
+            // throws an exception and the graphics engine then gets destroyed
+            // and reloaded between throw and catch (access violation in MSVC).
+            // That's why we abort completely and only display the exception.
+            COUT(0) << "An exception occurred during upgrade to graphics. "
+                    << "That is unrecoverable. The message was:" << endl
+                    << Exception::handleMessage() << endl;
+            abort();
+        }
 
         // Calls the InputManager which sets up the input devices.