Debugging with gdb not does not show origin of uncaught exception

1. Open a project configured with a MinGW-based kit.
2. Add a line like the following to the code:

   throw 123;
   

3. Run this in the debugger.
   The application will crash because of the uncaught exception. Creator will not point you to any code location. The only information about this will be a message box:
   

Creator should notice the uncaught exception and show the line from step 2 after the application crashed. With an MSVC-based kit and cdb this works fine. Other crashes, e.g. null-pointer deref, are handled well with gdb, too.