Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-11857

Debugging with gdb not does not show origin of uncaught exception

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Out of scope
    • Icon: Not Evaluated Not Evaluated
    • None
    • Qt Creator 3.0.0, Qt Creator 3.1.0-rc1
    • Debugger
    • Windows 7 64 bit
      MinGW g++ 4.4.0, 4.8.0
      gdb 7.5.1

      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.

        1. crashed.png
          crashed.png
          23 kB
        2. left.log
          0.7 kB
        3. right.log
          23 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            hjk hjk
            rlohning Robert Löhning
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes