[Bug 603716] Re: Crash reports still not useful
Philip Muškovac
yofel at gmx.net
Sun Jul 11 01:14:01 UTC 2010
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))]
** Changed in: kde4libs (Ubuntu)
Status: New => Confirmed
--
Crash reports still not useful
https://bugs.launchpad.net/bugs/603716
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde4libs in ubuntu.
More information about the kubuntu-bugs
mailing list