Bug 62991 - crash on exit, debugger may be active
Summary: crash on exit, debugger may be active
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: file create (show other bugs)
Version: git master
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-20 06:15 UTC by Jon Smirl
Modified: 2004-01-06 19:29 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Smirl 2003-08-20 06:15:35 UTC
Version:           CVS (using KDE KDE 3.1)
Installed from:    RedHat RPMs

I exited kdevelop. I think the debugger may have been active. Single copy of kdevelop running.

[New Thread 1096590304 (LWP 4632)]
0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0x40a2f57d in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#2  <signal handler called>
#3  0x41b2c461 in FileCreatePart::slotInitialize() ()
   from /opt/kde3/lib/kde3/libkdevfilecreate.so
#4  0x41b2cbbc in FileCreatePart::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/kde3/libkdevfilecreate.so
#5  0x40e7f0c9 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#6  0x4115e452 in QSignal::signal(QVariant const&) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#7  0x40e99158 in QSignal::activate() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#8  0x40ea00b3 in QSingleShotTimer::event(QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#9  0x40e20f24 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#10 0x40e20b19 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#11 0x409c31e9 in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdecore.so.4
#12 0x40dfbd95 in QEventLoop::activateTimers() ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#13 0x40dd98e8 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#14 0x40e34cf6 in QEventLoop::enterLoop() ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#15 0x40e34b98 in QEventLoop::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#16 0x40e21151 in QApplication::exec() ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#17 0x0806708b in main ()
#18 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6
Comment 1 Amilcar do Carmo Lucas 2003-11-01 19:51:19 UTC
I think this is no longer valid. Can you retest???
Comment 2 Jens Dagerbo 2003-11-07 00:46:39 UTC
Can't reproduce. Closing KDevelop both with the debugger running and in the "post-debugging-but-still-active" mode works fine - no crash.

(the "post-debugging-but-still-active" may be a bug though, but I dunno..)
Comment 3 Jens Dagerbo 2004-01-06 14:49:33 UTC
Still can't reproduce. Jon? Anyone? I'll close this one if noone can convince me otherwise..
Comment 4 Jon Smirl 2004-01-06 16:41:19 UTC
Let's close this one for now it is fairly old. I I hit it again I will refile with current stack trace.
Comment 5 Jens Dagerbo 2004-01-06 19:29:11 UTC
OK. Closing.