Bug 81680

Summary:	new project crashes on finishing the wizard
Product:	[Applications] kdevelop	Reporter:	Florian <qd75>
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version First Reported In:	3.0.1
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Florian 2004-05-16 13:31:18 UTC

Version:           3.0.1 (using KDE KDE 3.2.1)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7) 
OS:                Linux

I tried to make a controlcenter-addon-project.
When the wizard is on the last window, i can see the log-lines going on and then all windows crash and i get the "sigserv11"-window.

Code is:

This backtrace appears to be useless.
This is probably because your packages are built in a way which prevents creating of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
(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)...
(no debugging symbols found)...0x417d29cb in waitpid ()
   from /lib/libpthread.so.0
#0  0x417d29cb in waitpid () from /lib/libpthread.so.0
#1  0x40de0d14 in ?? () from /usr/kde/3.2/lib/libkdecore.so.4

But it seems that this is useless for you?

When i look in the project-home, there is a new project generated, but when i try to open this, it chrashes again.

As i saw, there where many "new project&crash"-bugs, but all related to version 2.xx, so i posted this.

Greets, qd

Comment 1 Jens Dagerbo 2004-05-20 14:22:19 UTC

Yes, the backtrace is useless.

Please update to the latest versions of kdelibs and kdevelop. I believe this problem is fixed.

Closing as INVALID as the report is probably a dupe of a solved report but doesn't contain enough information to be sure.

If updating doesn't help and you can provide a proper backtrace, please reopen.