When debugging an application, Q_ASSERTs and other abort()-related macros should be "handled" by the debugger.

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.