Bug: SIGSEV crash while debugging

Christopher crodrig at localhost.localdomain
Thu Mar 28 10:49:07 GMT 2002


I discovered that closing a window while the debugger is executing can crash 
Using KDE 2.2-10, KDevelop 2.2-11.

Here is a program (two files) that will generate the error:

void nuke();
int main()
	return 0;

void nuke()

Make a new project with these two files and build it.

Step through the program in debug mode until the arrow is pointing at the 
beginning of nuke(). Then, close the window 'nuke.cpp' and step again. This 
will generate an error and a stack trace similar to the following:

--stack trace starts here--
(no debugging symbols found)...0x411f5669 in __wait4 ()
   from /lib/i686/libc.so.6
#0  0x411f5669 in __wait4 () from /lib/i686/libc.so.6
#1  0x41271154 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x409c9838 in KCrash::defaultCrashHandler () at eval.c:41
#3  <signal handler called>
#4  0x0806d94e in CToolClass::writeToolConfig () at eval.c:41
#5  0x080a17e1 in CToolClass::writeToolConfig () at eval.c:41
#6  0x080819c6 in CToolClass::writeToolConfig () at eval.c:41
#7  0x4009940e in GDBController::showStepInSource (this=0x84aee38,
    t0=@0xbfffeae0, t1=31, t2=@0xbfffeaf0) at gdbcontroller.moc:413
#8  0x40092a85 in GDBController::parseProgramLocation (this=0x84aee38,
"/home/crodrig/src/crashtest/crashtest/main.cpp:31:1178:beg:0x8048543") at 
#9  0x4009390d in GDBController::parseCmdBlock (this=0x84aee38,
at gdbcontroller.cpp:997
#10 0x40093ba8 in GDBController::parse (this=0x84aee38,
    buf=0x84af9f0 "main (argc=1, argv=0xbffffa14) at main.cpp:31")
    at gdbcontroller.cpp:1082
#11 0x400963de in GDBController::slotDbgStdout (this=0x84aee38,
    buf=0xbfffece0 "main (argc=1, argv=0xbffffa14) at 
    buflen=119) at gdbcontroller.cpp:1613
#12 0x4097594e in KProcess::receivedStdout () at eval.c:41
#13 0x40a3415d in KProcess::childOutput () at eval.c:41
#14 0x40a33f20 in KProcess::slotChildOutput () at eval.c:41
#15 0x40cb8c81 in QObject::activate_signal ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#16 0x40d0da76 in QSocketNotifier::activated ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#17 0x40cebf67 in QSocketNotifier::event ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#18 0x40c68891 in QApplication::notify () from 
#19 0x40930c89 in KApplication::notify () at eval.c:41
#20 0x40c3312b in sn_activate () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#21 0x40c33999 in QApplication::processNextEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#22 0x40c6a74c in QApplication::enter_loop ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#23 0x40c33197 in QApplication::exec () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#24 0x080eb052 in CToolClass::writeToolConfig () at eval.c:41
#25 0x41157507 in __libc_start_main (
    main=0x80ea0f0 <CToolClass::writeToolConfig(QValueList<CToolApp> const 
&)+526464>, argc=7, ubp_av=0xbffff9d4, init=0x80621a4 <_init>,
    fini=0x81fd0b0 <_fini>, rtld_fini=0x4000dc14 <_dl_fini>,
    stack_end=0xbffff9cc) at ../sysdeps/generic/libc-start.c:129

to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«

More information about the KDevelop mailing list