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

Debugger: Display JS/QML stack frame when a Quick 2 application crashes/stops

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • Icon: P2: Important P2: Important
    • Qt Creator 3.3.0
    • Qt Creator 3.0.0
    • Debugger
    • None
    • Windows / Linux

    • qtdeclarative 33201dc147d03690fe8c744654245041c64197e6 (dev, 12.2.2014,5.3). Creator (gdb, infrastructure) e64fefdbc466b1247a2cee68617ad904d2388712 (3.1, 25.02.14) , CDB extension 437e593a8724db8d117c867f94a51f05f37f4b71 (3.1 26.2.2014)

      When a Quick2 application crashes, it is hard to find out from which QML file the crash originated. In the default case, the debugger just shows a bit of V4 stack and then a garbled trace. It would be good if the QML file could be shown.

      • A checkbox to set QV4_FORCE_INTERPRETER could be added (somewhere next to QML debugging in the run configuration . This would result in proper stack traces
      • The QML file/line number could be extracted from a variable of type QV4::ExecutionContext which can be found in the locals, or deduced from the stack pointer with some offset or by retrieving a register value. A free function taking that pointer and returning an allocated string of the form "file:line" could be added to QtQml (see ExecutionEngine::stackTrace(int frameLimit)). The debugger could then call that to open an editor at that point.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            kkohne Kai Köhne
            kleint Friedemann Kleint
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes