[Bug 62698] New: Crash when closing a project
Chris Thompson
chris at hypocrite.org
Fri Aug 15 03:05:08 UTC 2003
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=62698
Summary: Crash when closing a project
Product: kdevelop
Version: unspecified
Platform: Gentoo Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: kdevelop-devel at kdevelop.org
ReportedBy: chris at hypocrite.org
Version: 3.0a5 latest CVS (using KDE KDE 3.1.2)
Installed from: Gentoo Packages
OS: Linux
I start up KDevelop (Gideon 3.0a5, latest cvs). It automatically opens my previous project. I go to the project menu and select Close. KDevelop crashes. The same thing happens when I try to open a different project, presumably because it has to first close the current project.
This is happening with 100% reproducability. I updated from cvs today, normally do so every couple of days. I had never seen this before.
Here is my backtrace from gdb:
#0 0x00000000 in ?? ()
#1 0x409a3057 in KXMLGUI::ContainerNode::unplugActions(KXMLGUI::BuildState&)
() from /usr/kde/3.1/lib/libkdeui.so.4
#2 0x409a2aac in KXMLGUI::ContainerNode::destruct(QDomElement, KXMLGUI::BuildState&) () from /usr/kde/3.1/lib/libkdeui.so.4
#3 0x409a2cf3 in KXMLGUI::ContainerNode::destructChildren(QDomElement const&, KXMLGUI::BuildState&) () from /usr/kde/3.1/lib/libkdeui.so.4
#4 0x409a2a9d in KXMLGUI::ContainerNode::destruct(QDomElement, KXMLGUI::BuildState&) () from /usr/kde/3.1/lib/libkdeui.so.4
#5 0x409a2cf3 in KXMLGUI::ContainerNode::destructChildren(QDomElement const&, KXMLGUI::BuildState&) () from /usr/kde/3.1/lib/libkdeui.so.4
#6 0x409a2a9d in KXMLGUI::ContainerNode::destruct(QDomElement, KXMLGUI::BuildState&) () from /usr/kde/3.1/lib/libkdeui.so.4
#7 0x4099e737 in KXMLGUIFactory::removeClient(KXMLGUIClient*) ()
from /usr/kde/3.1/lib/libkdeui.so.4
#8 0x0809fef1 in PluginController::removePart(KXMLGUIClient*) (
this=0x81ee150, part=0x8b6d230) at plugincontroller.cpp:283
#9 0x0809c2ee in ProjectManager::unloadLanguageSupport() (this=0x81eb330)
at projectmanager.cpp:466
#10 0x0809aff6 in ProjectManager::closeProject() (this=0x81eb330)
at projectmanager.cpp:277
#11 0x0809d545 in ProjectManager::qt_invoke(int, QUObject*) (this=0x81eb330,
_id=4, _o=0xbfffea00) at projectmanager.moc:109
Here is what KCrash grabs, probably not useful:
[New Thread 16384 (LWP 16109)]
[New Thread 32769 (LWP 16115)]
[New Thread 16386 (LWP 16116)]
0x41425f88 in waitpid () from /lib/libpthread.so.0
#0 0x41425f88 in waitpid () from /lib/libpthread.so.0
#1 0x40b48a3e in KCrash::defaultCrashHandler(int) ()
from /usr/kde/3.1/lib/libkdecore.so.4
#2 0x41424dfa in __pthread_sighandler () from /lib/libpthread.so.0
#3 <signal handler called>
I have tried recompiling KDevelop (make clean, reconfigure, remake) both in release mode and in debug mode. The same problem occurs both times.
More information about the KDevelop-devel
mailing list