Comment 5 for bug 603716
Revision history for this message
| Philip Muškovac (yofel) wrote Re: Crash reports still not useful | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Confirmed, I just got a plasma crash for some reason and drkonq didn't want to retrace it, even trying your test:
$ kate &
[1] 6927
$ kill -SEGV 6927
does bring drkonqi up, but the backtrace is useless and doesn't match with the gdb output if I run 'gdb kate'. Or taking dolphin as an example, all I get is:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f6ad9877760 (LWP 27989))]