Version: (using KDE 4.4.1) Compiler: gcc-4.3 OS: Linux Installed from: Gentoo Packages When hitting a breakpoint, I frequently got a crash from kdevelop. Most of the threads don't have a meaningful backtrace, but the crashing thread does, and the backtrace is this one: Thread 1 (Thread 0x7ff08efa9740 (LWP 30944)): [KCrash Handler] #5 0x00007ff089db8315 in raise () from /lib/libc.so.6 #6 0x00007ff089db9811 in abort () from /lib/libc.so.6 #7 0x00007ff08b8f9b65 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007ff08b8f9d0d in ?? () from /usr/lib64/qt4/libQtCore.so.4 #9 0x00007ff08b8f9ea5 in qFatal(char const*, ...) () from /usr/lib64/qt4/libQtCore.so.4 #10 0x00007ff06f840e3e in KDevelop::GdbVariable::setVarobj (this=0x4a274b0, v=...) at /local/bschindler/projects/kdevelop/debuggers/gdb/gdbvariable.cpp:80 #11 0x00007ff06f844466 in CreateVarobjHandler::handle (this=0x497d140, r=...) at /local/bschindler/projects/kdevelop/debuggers/gdb/gdbvariable.cpp:104 #12 0x00007ff06f80a1ac in GDBDebugger::GDBCommand::invokeHandler (this=0x48f0520, r=...) at /local/bschindler/projects/kdevelop/debuggers/gdb/gdbcommand.cpp:80 #13 0x00007ff06f7fd7f8 in GDBDebugger::GDB::processLine (this=0x7ff0544eb800, line=...) at /local/bschindler/projects/kdevelop/debuggers/gdb/gdb.cpp:278 #14 0x00007ff06f7fe084 in GDBDebugger::GDB::readyReadStandardOutput (this=0x7ff0544eb800) at /local/bschindler/projects/kdevelop/debuggers/gdb/gdb.cpp:175 #15 0x00007ff06f7fc51b in GDBDebugger::GDB::qt_metacall (this=0x7ff0544eb800, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0x7fff28defd00) at /local/bschindler/build/kdevelop/debuggers/gdb/moc_gdb.cpp:111 #16 0x00007ff08ba09147 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #17 0x00007ff08b9941a8 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #18 0x00007ff08b994619 in QProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #19 0x00007ff08ea32e4d in KProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkdecore.so.5 #20 0x00007ff08ba09147 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #21 0x00007ff08ba5496e in QSocketNotifier::activated(int) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x00007ff08ba0fc73 in QSocketNotifier::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #23 0x00007ff08ac8dead in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #24 0x00007ff08ac96cd3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #25 0x00007ff08c19c22b in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #26 0x00007ff08b9f5d5b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #27 0x00007ff08ba1f8a9 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #28 0x00007ff084bf5d59 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #29 0x00007ff084bf95a8 in ?? () from /usr/lib/libglib-2.0.so.0 #30 0x00007ff084bf975c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #31 0x00007ff08ba1f50c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #32 0x00007ff08ad2b86f in ?? () from /usr/lib64/qt4/libQtGui.so.4 #33 0x00007ff08b9f4672 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #34 0x00007ff08b9f4a44 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #35 0x00007ff08b9f6ea6 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #36 0x00000000004081d0 in main (argc=1, argv=0x7fff28df2128) at /local/bschindler/projects/kdevelop/app/main_internal.cpp:222
Hmm, would be good to see the gdb communication output from this. Can you provide at least the output from the gdb debug area? run kdebugdialog, search for gdb, enable it. Then start kdevelop and redirect its output and error output to a file, hit the crash and post the file.
Can you provide the additional debug information Andreas asked for? Else we can't do anything about it. Thanks.
I'm right now in a deadline rush and switched to qtcreator. Even though it also has its many shortcomings, it actually works sufficiently fast and does not crash, so right now I cannot provide that info. Once this deadline is over (end of march), I'll try to reproduce and I'll post the info Sorry for the delay
ok, please reopen when you have the information.
*** This bug has been marked as a duplicate of bug 219570 ***