https://bugs.kde.org/show_bug.cgi?id=478287
Matt Fagnani <matt.fagn...@bell.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #2 from Matt Fagnani <matt.fagn...@bell.net> ---
(In reply to Harald Sitter from comment #1)
> I am not quite following. If gdb crashes drkonqi cannot possibly present a
> backtrace. Your expected result can just not happen, can it?
I expected that drkonqi wouldn't have crashed when creating a trace for the
plasmashell crash, which I didn't write but was implied, and then that drkonqi
would have shown the trace. plasma-plasmashell.service appeared to time out
when responding to SIGTERM in the journal message I included
"plasma-plasmashell.service: State 'stop-sigterm' timed out. Aborting"; that
message seemed to happen when drkonqi was creating the plasmashell trace which
usually was ongoing for at least 20 seconds when the crashes happened.
plasmashell, drkonqi, kioslave5, and gdb were aborted right after that based on
the plasma-plasmashell.service timeout. I'm unsure if that happened for all
such crashes, but it might explain the crashes I saw at least in part. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
