Qt silently fails at runtime when signals and slots are messed up. Turns out there is a way to force it to crash at runtime in these situations (and possibly others as well):
$ export QT_FATAL_WARNINGS=1 $ ./rosegarden
You won't get very far. ISTM that we should fix all of these, then turn this on by default at the very least for a debug build. This will let us catch horrible problems immediately rather than letting a release go with a serious flaw.
It appears that what this does is stop the application whenever a warning is written to the debug output via qWarning(). See the following page for more:
Log in to post a comment.