https://bugs.kde.org/show_bug.cgi?id=389100
--- Comment #2 from Michael Heidelbach <ottw...@gmail.com> --- (In reply to Milian Wolff from comment #1) > are you maybe using a debug build in KDevelop and a release build in Qt > Creator? $ file /usr/bin/kdevelop /usr/bin/kdevelop: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=a25f68e11f0df7e95e0881b060e3dc9fec6563bb, stripped 1) Before I tried this I had resetted KDev.-settings to defaults + removed everything from the environment. 2) In the meantime I tried using qtcreator with the previously saved enviroment settings from KDev. Now look: ``` ASSERT: "docId > 0" in file ... src/frameworks/baloo/src/engine/idfilenamedb.cpp, line 104 Das Programm ist abgestürzt. The process was ended forcefully. ... build/frameworks/baloo/bin/balooctl crashed. ``` So apparently my setup is borked. I haven't figured out what it is yet. > One way or another, the QtCreator behavior is the unexpected one, > you seem to be compiling without assertions there. Really? The app is expected to crash? How can I debug an application that doesn't pass Q_ASSERT(false). Is there a global flag or something to disable assertions and still have 'qDebug() << "bla";' work? I'm using c++/cmake et. al. only for 2 weeks now => zero..lowest experience. -- You are receiving this mail because: You are watching all bug changes.
