Details
-
Type:
Suggestion
-
Status: Closed
-
Priority:
Not Evaluated
-
Resolution: Duplicate
-
Affects Version/s: Qt Creator 2.3.0, Qt Creator 2.4.0
-
Fix Version/s: None
-
Component/s: Debugger
-
Labels:None
-
Environment:
Ms Windows 7 x64
Description
What's happening now:
If somewhere in the code a Q_ASSERT() evaluates false, the application is stopped with an info, where the Q_ASSERT() is and what expression evaluates false. If the application was run with a debugger, debugger is also stopped. If the developer wants to inspect a call stack, he must call qInstallMsgHandler() with a new MsgHandler, set a breakpoint in it and reproduce the bug. This is somewhat cumbersome.
What would be nice to happen:
Debugger breaks application execution in such case, giving the developer a way to inspect the call stack etc.
Attachments
Issue Links
- relates to
-
QTCREATORBUG-5200 Fix "Internal error: pc 0x0 in read in psymtab, but not in symtab."
-
- Closed
-