Bug 83190

Summary:	Import of projects crash's kdevelop
Product:	[Applications] kdevelop	Reporter:	Danny Spangenberg <danny.spangenberg>
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED NOT A BUG
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Danny Spangenberg 2004-06-11 01:36:40 UTC

Version:           3.0.4 (using KDE 3.2.3, compiled sources)
Compiler:          gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
OS:                Linux (i686) release 2.4.26

Everytime I try to import a project e. g. bookcase-0.9.3 or pwmanager-0.7 kdevelop crashs.

Directory: /home/dspangenberg/work/kde/apps/bookcase-0.9.3
Project name: bookcase
Project type: Generic C++ Application (Automake based)
Author: Danny Spangenberg
EMail: dspangenberg@notebook

Kdevelop close the dialog, in the status bar appears "Updating..." and then it crashs. Importing pwmanager shortly shows a progress bar before crashing.

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".
0x418a79cb in ?? ()
#0  0x418a79cb in ?? ()
#1  0x40eabc5c in ?? ()

Comment 1 Mac Michaels 2004-06-12 15:16:03 UTC

I get this result when importing wine CVS files in version 3.2.2 of kdevelop.
The status bar appears and shows continusing progress for about 30 seconds then everything disappears. I don't even get a crash window popup.

Comment 2 Mac Michaels 2004-06-12 15:43:11 UTC

Correction of previous comment: I am using kdevelop version 3.0.3 under kde 3.2.2. Sorry about that.

Comment 3 Jens Dagerbo 2004-06-13 03:06:49 UTC

I'm sorry, but "it crashed" isn't much of a bug report.

This report gives us no more information than that it crashed on your system. There is no indication what might have been the cause of the crash. Without such info, we stand little chance of finding the problem, and if we happen on a problem and fix it, we still have no idea if this was the cause of this crash. 

So, it's either close it now or leave it in the bug database as noise forever.

I opt for the former. Please reopen if you can get a backtrace, and it's not an already reported problem.

Closing as INVALID.