On 10/11/2013 06:14 PM, Repository Rosegarden code wrote:
> Comment out Q_ASSERT, as it is plainly not safe to use in production code.
Yikes. This is not good. I've just verified it. It appears to be a
problem with our configure.ac. This:
RG_DEFINES_RELEASE="-DNDEBUG -DBUILD_RELEASE -DNO_TIMING"
Needs to define QT_NO_DEBUG. I'm going to try it out and commit.
Then it should be safe to use Q_ASSERT().