redirect qDebug() to file

[fullmetalcoder]

Also it is recommended to "handle" fatal messages (using abort() or exit(-1) or something akin) because that's what the default handler does and if you don't do it you're likely to end up with segfaults instead (though not necessarily at the same place so you may have a hard time tracking the bugs...).

[spirit]

Also it is recommended to "handle" fatal messages (using abort() or exit(-1) or something akin) because that's what the default handler does and if you don't do it you're likely to end up with segfaults instead (though not necessarily at the same place so you may have a hard time tracking the bugs...).

...
     case QtFatalMsg:
        txt = QString("Fatal: %1").arg(msg);
        abort();
...

...
     case QtFatalMsg:
        txt = QString("Fatal: %1").arg(msg);
        abort();
...

To copy to clipboard, switch view to plain text mode 

[faldzip]

Qt is using that handler in the function qt_message_output() and then it's checking if the message is QtFatalMsg and generating core dump or sth, so there is no need to implement it in addition to that. Whats more it's more complicated on Windows (with msvc) than just abort() in default implementation.

[fullmetalcoder]

...
     case QtFatalMsg:
        txt = QString("Fatal: %1").arg(msg);
        abort();
...

...
     case QtFatalMsg:
        txt = QString("Fatal: %1").arg(msg);
        abort();
...

To copy to clipboard, switch view to plain text mode 

Sorry missed that one line, I was in a bit of a rush when I read your post...