Bug 62407

Summary: Gideon CVS crashes when creating a new project
Product: [Applications] kdevelop Reporter: Dustan Ashley <dusty00>
Component: generalAssignee: KDevelop Developers <kdevelop-devel>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dustan Ashley 2003-08-09 06:06:59 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 3.2.3 20030422 
OS:          Linux

When attempting to create a new project in Gideon CVS (shapshot current as of this evening) KDevelop will crash after it creates the project files. The backtrace is as follows:


(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 16384 (LWP 12420)]
0x418881c7 in waitpid ()
   from /lib/libpthread.so.0
#0  0x418881c7 in waitpid () from /lib/libpthread.so.0
Comment 1 Amilcar do Carmo Lucas 2003-08-11 09:48:20 UTC
This bug report is completly useless as it is: 
- I can not reproduce it here (you don't explain what type of new project) 
- You don't tell your QT version 
- You don't tell your KDE version 
- The backtrace is useless! 
 
Please give some more info 
Comment 2 Alexandros Karypidis 2003-08-18 16:25:28 UTC
I also have the same problem. It seems to be related to OPENING, not creating a 
project (I crash even when opening an existing project). 
 
Here is the backtrace: 
 
[New Thread 16384 (LWP 14113)] 
[New Thread 32769 (LWP 14124)] 
[New Thread 16386 (LWP 14125)] 
0x414ec3ba in waitpid () from /lib/libpthread.so.0 
#0  0x414ec3ba in waitpid () from /lib/libpthread.so.0 
#1  0x40c00ad9 in KCrash::defaultCrashHandler(int) () 
   from /opt/kde3/lib/libkdecore.so.4 
#2  0x414eb1ec in __pthread_sighandler () from /lib/libpthread.so.0 
#3  <signal handler called> 
#4  0x086b864a in ?? () 
#5  0x40a61cec in KXMLGUI::ContainerNode::destruct(QDomElement, 
KXMLGUI::BuildState&) () from /opt/kde3/lib/libkdeui.so.4 
#6  0x40a61eea in KXMLGUI::ContainerNode::destructChildren(QDomElement const&, 
KXMLGUI::BuildState&) () from /opt/kde3/lib/libkdeui.so.4 
#7  0x40a61ce0 in KXMLGUI::ContainerNode::destruct(QDomElement, 
KXMLGUI::BuildState&) () from /opt/kde3/lib/libkdeui.so.4 
#8  0x40a61eea in KXMLGUI::ContainerNode::destructChildren(QDomElement const&, 
KXMLGUI::BuildState&) () from /opt/kde3/lib/libkdeui.so.4 
#9  0x40a61ce0 in KXMLGUI::ContainerNode::destruct(QDomElement, 
KXMLGUI::BuildState&) () from /opt/kde3/lib/libkdeui.so.4 
#10 0x40a5f08e in KXMLGUIFactory::removeClient(KXMLGUIClient*) () 
   from /opt/kde3/lib/libkdeui.so.4 
#11 0x08081fba in PluginController::removePart(KXMLGUIClient*) ( 
    this=0x819a3c8, part=0x8b7a9a8) at plugincontroller.cpp:283 
#12 0x0807e2e7 in ProjectManager::unloadLanguageSupport() (this=0x81a46e8) 
    at projectmanager.cpp:466 
#13 0x0807cfbc in ProjectManager::closeProject() (this=0x81a46e8) 
    at projectmanager.cpp:277 
#14 0x0807cb33 in ProjectManager::loadProject(KURL const&) (this=0x81a46e8,  
    url=@0xbfffe630) at projectmanager.cpp:204 
#15 0x0807c59b in ProjectManager::slotOpenProject() (this=0x81a46e8) 
    at projectmanager.cpp:132 
#16 0x0807f5e3 in ProjectManager::qt_invoke(int, QUObject*) (this=0x81a46e8,  
    _id=5, _o=0xbfffe730) at projectmanager.moc:110 
#17 0x40f8f3b7 in QObject::activate_signal(QConnectionList*, QUObject*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#18 0x40f8f25f in QObject::activate_signal(int) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#19 0x409aca99 in KAction::activated() () from /opt/kde3/lib/libkdeui.so.4 
#20 0x4099d58d in KAction::slotActivated() () from /opt/kde3/lib/libkdeui.so.4 
#21 0x409acb51 in KAction::qt_invoke(int, QUObject*) () 
   from /opt/kde3/lib/libkdeui.so.4 
#22 0x40f8f3b7 in QObject::activate_signal(QConnectionList*, QUObject*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#23 0x412877aa in QSignal::signal(QVariant const&) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#24 0x40fa9f48 in QSignal::activate() () from /usr/lib/qt3/lib/libqt-mt.so.3 
#25 0x410859eb in QPopupMenu::mouseReleaseEvent(QMouseEvent*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#26 0x40fc5634 in QWidget::event(QEvent*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#27 0x40f2dee8 in QApplication::internalNotify(QObject*, QEvent*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#28 0x40f2d5ee in QApplication::notify(QObject*, QEvent*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#29 0x40b8bc19 in KApplication::notify(QObject*, QEvent*) () 
   from /opt/kde3/lib/libkdecore.so.4 
#30 0x40ecee76 in QETWidget::translateMouseEvent(_XEvent const*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#31 0x40ecc590 in QApplication::x11ProcessEvent(_XEvent*) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#32 0x40ee1aad in QEventLoop::processEvents(unsigned) () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#33 0x40f42583 in QEventLoop::enterLoop() () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#34 0x40f42476 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 
#35 0x40f2e16f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 
#36 0x0806a502 in main (argc=7, argv=0xbffff2f4) at main.cpp:125 
#37 0x4164c857 in __libc_start_main () from /lib/libc.so.6 
 
 
Comment 3 Alexandros Karypidis 2003-08-18 16:26:52 UTC
By the way, I am running KDE 3.1.3 (SuSE RPMs) with Qt 3.1.2 
Comment 4 Chris Thompson 2003-08-18 16:38:04 UTC
This is a duplicate of bug 62698 (or vice versa), I believe.  The stack traces look awfully 
similar. 
 
Comment 5 Alexandros Karypidis 2003-08-18 16:48:20 UTC
Chris is right. I was actually the victim of bug 62698. But I am not sure they 
are duplicates. The trace I gave IS identical to 62698, but one can't be 
certain that Dusty Ashley who originally reported it would have had the same 
trace as me... 
Comment 6 Jens Dagerbo 2003-08-18 16:53:26 UTC
Seems likely enough. :)  
 
Closing as dupe. 

*** This bug has been marked as a duplicate of 62698 ***
Comment 7 Alexandros Karypidis 2003-08-18 16:57:14 UTC
On the other hand, Chris must be right: 
 
I DO get a crash when creating a new project while having another project 
ALREADY open, whereas if I have no other project open, I can generate a new 
project just fine. The backtrace (follows) does seem to indicate that it is the 
same bug: 
 
[New Thread 16384 (LWP 4167)] 
[New Thread 32769 (LWP 4360)] 
[New Thread 16386 (LWP 4361)] 
0x414ec3ba in waitpid () from /lib/libpthread.so.0 
#0  0x414ec3ba in waitpid () from /lib/libpthread.so.0 
#1  0x40c00ad9 in KCrash::defaultCrashHandler(int) () 
   from /opt/kde3/lib/libkdecore.so.4 
#2  0x414eb1ec in __pthread_sighandler () from /lib/libpthread.so.0 
#3  <signal handler called> 
 
 
 
So, they probably are dupes after all...