tags:

views:

224

answers:

2

When I hit a normal assert statement while debugging with Visual Studio I get the option to break into the debugger so I can see the entire stack trace and the local variables, not just the assert message.

Is it possible to do this with Qt Creator+mingw32 and Q_ASSERT/Q_ASSERT_X?

A: 

It's possible. I have coded a BreakInDebugger function by hand and an assert macro that calls the function.

e.g: #define MyAssert(X) (BreakInDebugger();Q_ASSERT(X))

rpg
A: 

You can install a handler for the messages/warnings that Qt emits, and do your own processing of them. See the documentation for qInstallMsgHandler and the example they give there. It should be easy to insert a break in a custom message handler (or indeed, just assert on your own at that point). The one small drawback is that you'll be a bit further on down the stack than where the error actually occurred, but it is a simple matter to just step up the stack until you are at the proper frame.

Caleb Huitt - cjhuitt
I used the example with __asm("int3") before the abort() call and it works great.
Dan Berindei