[Bug 71764] New: no more stack traces from KDE crash handler

[Jon Smirl]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=71764     
           Summary: no more stack traces from KDE crash handler
           Product: kdevelop
           Version: CVS
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: jonsmirl at yahoo.com


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.