Bug 58895 - stop button can crash gideon in some cases
Summary: stop button can crash gideon in some cases
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-24 17:19 UTC by Jens Dagerbo
Modified: 2003-05-25 16:39 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 Jens Dagerbo 2003-05-24 17:19:10 UTC
Version:            (using KDE KDE 3.1.1a)
Installed from:    Compiled From Sources
Compiler:          gcc version 3.2.2
OS:          Linux (i686) release 2.4.20-gentoo-r3

How's that for a meaningless description? :)

I was debugging, absentmindedly closed the debugged program,
then attempted to stop the debugger with the "stop button"
-> crash.

It's fairly obvious from the trace what happens, but I haven't looked into _why_ yet.

[New Thread 16384 (LWP 1829)]
[New Thread 32769 (LWP 1845)]
[New Thread 32770 (LWP 2020)]
0x413a339c in waitpid () from /lib/libpthread.so.0
#0  0x413a339c in waitpid () from /lib/libpthread.so.0
#1  0x40ad3300 in KCrash::defaultCrashHandler(int) ()
   from /opt/kdecvs/lib/libkdecore.so.4
#2  0x413a217c in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x410cc499 in QString::QString(QString const&) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#5  0x080af3f5 in KDevPlugin::pluginName() const (this=0x87b4bf0)
    at kdevplugin.cpp:46
#6  0x080979d7 in MainWindowShare::slotStopMenuAboutToShow() (this=0x8161208)
    at mainwindowshare.cpp:271
#7  0x08098e52 in MainWindowShare::qt_invoke(int, QUObject*) (this=0x8161208, 
    _id=11, _o=0xbfffeca0) at mainwindowshare.moc:180
#8  0x40e50c39 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#9  0x40e50add in QObject::activate_signal(int) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#10 0x4114461e in QPopupMenu::aboutToShow() ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#11 0x40f3a0ea in QPopupMenu::popup(QPoint const&, int) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#12 0x409108c8 in KToolBarButton::showMenu() ()
   from /opt/kdecvs/lib/libkdeui.so.4
#13 0x409109c3 in KToolBarButton::slotDelayTimeout() ()
   from /opt/kdecvs/lib/libkdeui.so.4
#14 0x409113b0 in KToolBarButton::qt_invoke(int, QUObject*) ()
   from /opt/kdecvs/lib/libkdeui.so.4
#15 0x40e50c39 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#16 0x40e50add in QObject::activate_signal(int) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#17 0x411321cb in QTimer::timeout() () from /opt/qt-copy/lib/libqt-mt.so.3
#18 0x40e71d82 in QTimer::event(QEvent*) () from /opt/qt-copy/lib/libqt-mt.so.3
#19 0x40df2b04 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#20 0x40df22cb in QApplication::notify(QObject*, QEvent*) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#21 0x40a455f9 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kdecvs/lib/libkdecore.so.4
#22 0x40dcd903 in QEventLoop::activateTimers() ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#23 0x40dab188 in QEventLoop::processEvents(unsigned) ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#24 0x40e069a6 in QEventLoop::enterLoop() ()
   from /opt/qt-copy/lib/libqt-mt.so.3
#25 0x40e06848 in QEventLoop::exec() () from /opt/qt-copy/lib/libqt-mt.so.3
#26 0x40df2d31 in QApplication::exec() () from /opt/qt-copy/lib/libqt-mt.so.3
#27 0x08070f02 in main (argc=1, argv=0xbffff674) at main.cpp:124
#28 0x41516b47 in __libc_start_main () from /lib/libc.so.6
Comment 1 Harald Fernengel 2003-05-25 16:39:43 UTC
Fixed in CVS, the debugger stops now if the project gets unloaded. I think that's a better 
solution than to store SmartPointers.