[Bug 603716] Re: Crash reports still not useful

2010-07-10 Thread Kees Cook
When I clicked the Developer Information tab for crashes, I see a full backtrace. For example: $ kate [1] 6927 $ kill -SEGV 6927 And drkonqi shows the crash. Perhaps I'm missing something? What do you see when an application crashes? -- Crash reports still not useful

Re: [Bug 603716] Re: Crash reports still not useful

2010-07-10 Thread Scott Kitterman
What I copied in the bug was all I got. Scott Kitterman -- 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. -- kubuntu-bugs mailing list

[Bug 603716] Re: Crash reports still not useful

2010-07-10 Thread Philip Muškovac
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,

[Bug 603716] Re: Crash reports still not useful

2010-07-10 Thread Philip Muškovac
$ uname -a Linux yofel-t510 2.6.35-7-generic #12-Ubuntu SMP Fri Jul 9 21:54:03 UTC 2010 x86_64 GNU/Linux -- 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