Bug 156714 - KDevelop crashed when debugging
Summary: KDevelop crashed when debugging
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 3.5.0
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2008-01-26 14:23 UTC by András Manţia
Modified: 2018-10-21 04:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description András Manţia 2008-01-26 14:23:45 UTC
Using gdb CVS from yesterday, KDevelop crashes when debugging. I removed two
watch variables and one variable from the evaluation list, tried to step to the
next line, when it crashed. Here's the backtrace:
[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x2b71c09188e0 (LWP 15533)]
[New Thread 0x40800950 (LWP 15899)]
[New Thread 0x41001950 (LWP 15886)]
[KCrash handler]
#5  0x00002b71bc4564ab in QObject::connect ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#6  0x00002aaaac39d3a1 in QGuardedPtr (this=0xc9592e0, o=0xb1ab690)
    at /usr/lib64/qt3/include/qguardedptr.h:74
#7  0x00002aaaac3af3d8 in GDBCommand<GDBDebugger::VarItem> (this=0xc9592d0, 
    command=<value optimized out>, handler_this=0xb1ab690, 
    handler_method=0x2aaaac3a6680
<GDBDebugger::VarItem::valueDone(GDBMI::ResultRecord const&)>,
handlesError=true)
    at
/data/development/sources/kde-3.5/kdevelop/languages/cpp/debugger/gdbcommand.h:
#8  0x00002aaaac3a5cb1 in GDBDebugger::VarItem::updateValue (this=0xb1ab690)
    at
/data/development/sources/kde-3.5/kdevelop/languages/cpp/debugger/variablewidge
#9  0x00002aaaac3a9bf0 in GDBDebugger::VariableTree::handleVarUpdate (
    this=0x1d498f0, r=<value optimized out>)
    at
/data/development/sources/kde-3.5/kdevelop/languages/cpp/debugger/variablewidge
#10 0x00002aaaac39da46 in GDBDebugger::GDBCommand::invokeHandler (
    this=0xd97ebc0, r=@0x93a67e0)
    at
/data/development/sources/kde-3.5/kdevelop/languages/cpp/debugger/gdbcommand.cp
#11 0x00002aaaac399f0e in GDBDebugger::GDBController::processMICommandResponse
    (this=0x1d15c70, result=@0x93a67e0)
    at
/data/development/sources/kde-3.5/kdevelop/languages/cpp/debugger/gdbcontroller
#12 0x00002aaaac39a3ef in GDBDebugger::GDBController::slotDbgStdout (
    this=0x1d15c70, buf=<value optimized out>, buflen=<value optimized out>)
    at
/data/development/sources/kde-3.5/kdevelop/languages/cpp/debugger/gdbcontroller
#13 0x00002aaaac396383 in GDBDebugger::GDBController::qt_invoke (
    this=0x1d15c70, _id=<value optimized out>, _o=0x7ffff43063a0)
    at ./languages/cpp/debugger/gdbcontroller.moc:234
#14 0x00002b71bc453f6c in QObject::activate_signal ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#15 0x00002b71bb0aab6b in KProcess::receivedStdout (
    this=<value optimized out>, t0=0xcfecff0, 
    t1=0x7ffff4306440 "^done,changelist=[]\n(gdb) \n", t2=27)
    at ./kdecore/kprocess.moc:152
#16 0x00002b71bb0ab7de in KProcess::childOutput (this=0xcfecff0, 
    fdno=<value optimized out>)
    at /data/development/sources/kde-3.5/kdelibs/kdecore/kprocess.cpp:853
#17 0x00002b71bb0ab809 in KProcess::slotChildOutput (this=0xb1ab690, 
    fdno=-1133029173)
    at /data/development/sources/kde-3.5/kdelibs/kdecore/kprocess.cpp:733
#18 0x00002b71bb0abb64 in KProcess::qt_invoke (this=0xcfecff0, _id=2, 
    _o=0x7ffff43068f0) at ./kdecore/kprocess.moc:201
#19 0x00002b71bc453f6c in QObject::activate_signal ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#20 0x00002b71bc454624 in QObject::activate_signal ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#21 0x00002b71bc46e04b in QSocketNotifier::event ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#22 0x00002b71bc3fd7dd in QApplication::internalNotify ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#23 0x00002b71bc3fe4f8 in QApplication::notify ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#24 0x00002b71bb07be16 in KApplication::notify (this=0x7ffff4306e40, 
    receiver=0xae93d10, event=0x7ffff4306bf0)
    at /data/development/sources/kde-3.5/kdelibs/kdecore/kapplication.cpp:550
#25 0x00002b71bc3f35a3 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#26 0x00002b71bc3b3a54 in QEventLoop::processEvents ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#27 0x00002b71bc412053 in QEventLoop::enterLoop ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#28 0x00002b71bc411f02 in QEventLoop::exec ()
   from /usr/lib64/qt3/lib64/libqt-mt.so.3
#29 0x0000000000408a0a in main (argc=<value optimized out>, 
    argv=<value optimized out>)
    at /data/development/sources/kde-3.5/kdevelop/src/main.cpp:143
Comment 1 Dario Andres 2009-05-29 20:30:18 UTC
Is this still happening with a current KDevelop version ? Thanks
Comment 2 Andrew Crouthamel 2018-09-19 04:27:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-21 04:51:03 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!