Bug 71765

Summary:	no more stack traces from KDE crash handler
Product:	[Applications] kdevelop	Reporter:	Jon Smirl <jonsmirl>
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	git master
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jon Smirl 2004-01-03 19:04:03 UTC

Version:           CVS (using KDE Devel)
Installed from:    Compiled sources

I am using an update to date Fedora core and 2.6 kernel with KDE CVS. I have not been able to get stack traces from the KDE crash handler for several months now. The crash handler may need to be adjusted for TLS changes made by Redhat. For example I just crashed kdevelop and got this:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1088776224 (LWP 5417)]
[New Thread 1109752752 (LWP 5430)]
0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbfffd46c in ?? ()

I am sure that I am built debug with symbols. 0xffffe410 does not look like a valid address.

Comment 1 Jens Dagerbo 2004-01-03 19:07:57 UTC

Filed twice.

*** This bug has been marked as a duplicate of 71764 ***