[hardy] gdb error during KDE4 crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdb (Ubuntu) |
Invalid
|
Low
|
Rich Johnson |
Bug Description
I tried to reboot my computer from KDE4, but instead a window popped up, telling me that KNotify crashed.
Even though that it says that the backtrace is of no use, I suspect that it's of no use for finding bugs in KNotify, but it's valuable for gdb?
Here's the text in the "Backtrace" tab in the "KDE Crash Handler":
---
This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
/build/
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
/build/
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
---
By chance do you have the kdelibs5-dbg package installed? This may help provide better information on the report in the future. Has this happened to you more than once? I will definitely keep an eye on this and see if I can get KNotify to crash here. Rebooting, logging out, and shutting down are the 3 things that haven't caused me a bit of problems yet with KDE 4.