Bug 71765 - no more stack traces from KDE crash handler
Summary: no more stack traces from KDE crash handler
Status: RESOLVED DUPLICATE of bug 71764
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: git master
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-03 19:04 UTC by Jon Smirl
Modified: 2004-01-03 19:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
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 ***