https://bugs.kde.org/show_bug.cgi?id=448874

--- Comment #14 from andrea.i...@gmail.com ---
(In reply to Nate Graham from comment #13)
> Indeed it's not useful, because there's no backtrace. :) When plasma
> crashes, you need to type `bt` in the GDB prompt.
> 
> However I see now that you said the whole session crashed; if so that means
> that kwin_wayland is the thing that crashed, not plasmashell. So we would
> need a backtrace of the last kwin_wayland crash. you can use `coredumpctl`
> for this; see
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl

Hi again Pointiest,
actually the session does not crash, all running apps stay alive and usable
(Krunner as well). I will update the title to reflect this.

Now to the bt command, when I type it after attaching gdb to the plasmashell
process and triggering the crash of plasmashell, it only says:
`No stack.`

Hereafter the last part of gdb until the crash + backtrace. Could you please
advise further? Thanks!

[Thread 0x7fffc2ffd640 (LWP 9911) exited]
[Thread 0x7fffbb7fe640 (LWP 9908) exited]
[Thread 0x7fffc3fff640 (LWP 9907) exited]
[Thread 0x7fffd882c640 (LWP 9906) exited]
[Thread 0x7fffd902d640 (LWP 9905) exited]
[Thread 0x7fffd982e640 (LWP 9904) exited]
[Thread 0x7fffda02f640 (LWP 9903) exited]
[Thread 0x7fffecaa8640 (LWP 9902) exited]
[Thread 0x7fffefe75640 (LWP 9901) exited]
[Thread 0x7ffff0676640 (LWP 9900) exited]
[Thread 0x7ffff0e77640 (LWP 9899) exited]
[Thread 0x7ffff3117980 (LWP 9860) exited]
[Inferior 1 (process 9860) exited with code 01]
(gdb) backtrace
No stack.
(gdb)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to