Bug 46618 - Crash while debug single stepping
Summary: Crash while debug single stepping
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 2.1.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-18 18:33 UTC by David Jarvie
Modified: 2003-06-06 22:35 UTC (History)
0 users

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 David Jarvie 2002-08-18 18:19:13 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           KDE 3.0.2 
Severity:          crash
Installed from:    SuSE RPMs
Compiler:          gcc 2.95.3
OS:                Linux
OS/Compiler notes: SuSE 7.2 i386

I was debugging my application single stepping at the time when KDevelop crashed. The trace is:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 25098)]
0x414b9279 in wait4 () from /lib/libc.so.6
#0  0x414b9279 in wait4 () from /lib/libc.so.6
#1  0x415272c8 in __DTOR_END__ () from /lib/libc.so.6
#2  0x413d4317 in waitpid () from /lib/libpthread.so.0
#3  0x40b1cd1c in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x413d1e9d in pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x4009d186 in GDBController::parseRequestedData ()
   from /opt/kde3/lib/libkdevelopdbg.so.2
#7  0x4009d8dd in GDBController::parseCmdBlock ()
   from /opt/kde3/lib/libkdevelopdbg.so.2
#8  0x4009db37 in GDBController::parse ()
   from /opt/kde3/lib/libkdevelopdbg.so.2
#9  0x400a03fb in GDBController::slotDbgStdout ()
   from /opt/kde3/lib/libkdevelopdbg.so.2
#10 0x400a13a8 in GDBController::qt_invoke ()
   from /opt/kde3/lib/libkdevelopdbg.so.2
#11 0x40e77484 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#12 0x40abbc7d in KProcess::receivedStdout ()
   from /opt/kde3/lib/libkdecore.so.4
#13 0x40abcb3a in KProcess::childOutput () from /opt/kde3/lib/libkdecore.so.4
#14 0x40abc163 in KProcess::qt_invoke () from /opt/kde3/lib/libkdecore.so.4
#15 0x40e77484 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40e7759f in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x4112b6ed in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x40e8d9af in QSocketNotifier::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40e1d1b6 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40e1d054 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x40a77267 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#22 0x40dc8cbd in sn_activate () from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40dc94a7 in QApplication::processNextEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40e1e692 in QApplication::enter_loop ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40dc8d3b in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x811ade9 in main ()
#27 0x4142cc5f in __libc_start_main () from /lib/libc.so.6


(Submitted via bugs.kde.org)
Comment 1 John Birch 2003-06-06 22:35:33 UTC
Hmmm - my apoligies for not seeing this bug early 
 
kdevelop2.1.3 is not maintained - maybe updating to the last stable version 
(2.1.5) could fix this, but I'm not sure. 
 
Note that we're no longer maintaining this version, so instead try kdevelop 
version 3 - I really recommend the cvs version. This has much better support 
for projects and many fixes in the debugger.