https://bugs.kde.org/show_bug.cgi?id=515510
--- Comment #8 from Dm <[email protected]> --- (In reply to cwo from comment #3) > Q_ASSERT_X will cause a crash if its conditions are not met in a debug > build, but do nothing in a release build. Q_ASSERT_X will also print an > error message with more information about the problem to the console (or if > it's not running in a console, to the system log – at least on most systemd > configurations). > > Could you reproduce the error, then run `journalctl --reverse` and copy the > assert message from there and paste it here? May be, KDE devs have any "disarmed" versions/setups of QT or something else with Q_ASSERT doesn't stop with SIGABRT and no such setup in Neon User Release? For me, only -DQT_NO_DEBUG helps -- You are receiving this mail because: You are watching all bug changes.
