Bug#44567: KDevelop reproducibly crashes when debugging empty program

inkclerks at rinkworks.com inkclerks at rinkworks.com
Mon Jul 1 00:04:03 UTC 2002


Package: kdevelop
Version: 2.1 (using KDE 3.0.1 )
Severity: crash
Installed from:    Compiled From Sources
Compiler:          egcs 2.96
OS:                Linux
OS/Compiler notes: Not Specified

This error is in KDevelop 2.1, the same problem existed in an earlier version of KDevelop.

To produce this error, create a C terminal KDevelop project. Add a c file with these contents (note, it has to be a separate file):

void nuke()
{
}

then modify the main.c to look like this:

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

Build the project. Put a breakpoint on the call to nuke() and debug the program. Step into the function nuke() and then close the window with the function nuke(). Step again and KDevelop will crash.

The backtrace is as follows:
[New Thread 1024 (LWP 9492)]
0x41451669 in __wait4 () from /lib/i686/libc.so.6
#0  0x41451669 in __wait4 () from /lib/i686/libc.so.6
#1  0x414cd154 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x41358523 in waitpid (pid=12910, stat_loc=0x0, options=0)
    at wrapsyscall.c:172
#3  0x40ada9d5 in KCrash::defaultCrashHandler () at eval.c:41
#4  0x413568d5 in pthread_sighandler (signo=11, ctx=
      {gs = 7, __gsh = 0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 49168, edi = 137288240, esi = 0, ebp = 3221218600, esp = 3221218588, ebx = 1074180748, edx = 1, ecx = 0, eax = 137423016, trapno = 14, err = 4, eip = 1074037785, cs = 35, __csh = 0, eflags = 66066, esp_at_signal = 3221218588, ss = 43, __ssh = 0, fpstate = 0xbfffe2a0, oldmask = 2147483648, cr2 = 252}) at signals.c:97
#5  <signal handler called>
#6  0x40048419 in KWrite::clearStepLine () at eval.c:41
#7  0x080bcc24 in CKDevelop::slotDebugShowStepInSource () at eval.c:41
#8  0x081ebe83 in CKDevelop::qt_invoke () at eval.c:41
#9  0x40e0b71a in QObject::activate_signal ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#10 0x4009a4c8 in GDBController::showStepInSource () at eval.c:41
#11 0x4009691f in GDBController::parseProgramLocation () at eval.c:41
#12 0x40097744 in GDBController::parseCmdBlock () at eval.c:41
#13 0x400979cb in GDBController::parse () at eval.c:41
#14 0x4009a0d7 in GDBController::slotDbgStdout () at eval.c:41
#15 0x4009aeb3 in GDBController::qt_invoke () at eval.c:41
#16 0x40e0b6c6 in QObject::activate_signal ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#17 0x40a74009 in KProcess::receivedStdout () at eval.c:41
#18 0x40a72929 in KProcess::childOutput () at eval.c:41
#19 0x40a727a4 in KProcess::slotChildOutput () at eval.c:41
#20 0x40a742d0 in KProcess::qt_invoke () at eval.c:41
#21 0x40e0b6c6 in QObject::activate_signal ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#22 0x40e0b7cb in QObject::activate_signal ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#23 0x410b8e3f in QSocketNotifier::activated ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#24 0x40e20932 in QSocketNotifier::event ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#25 0x40db7854 in QApplication::internalNotify ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#26 0x40db76fb in QApplication::notify ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#27 0x40a328ea in KApplication::notify () at eval.c:41
#28 0x40d636e0 in sn_activate () from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#29 0x40d63f7d in QApplication::processNextEvent ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#30 0x40db8bc0 in QApplication::enter_loop ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#31 0x40d63748 in QApplication::exec ()
   from /usr/lib/qt-3.0.4/lib/libqt-mt.so.3
#32 0x0812a2ad in main () at eval.c:41
#33 0x413b3507 in __libc_start_main (main=0x8129840 <main>, argc=7, 
    ubp_av=0xbffff834, init=0x80656d8 <_init>, fini=0x8243e98 <_fini>, 
    rtld_fini=0x4000dc14 <_dl_fini>, stack_end=0xbffff82c)
    at ../sysdeps/generic/libc-start.c:129


(Submitted via bugs.kde.org)


(Complete bug history is available at http://bugs.kde.org/db/44/44567.html)




More information about the KDevelop-devel mailing list