https://bugs.kde.org/show_bug.cgi?id=494650
--- Comment #6 from Mark <mark.coet...@gmail.com> --- (In reply to TraceyC from comment #5) > The list of the coredumps on your system doesn't give us the information we > need. What we need is a backtrace of *one* coredump - the one that > corresponds to the last time the system froze. Please read through this to > find out how to do that: > > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl I'm at a loss.. Subsequent coredumps (<coredumpctl --reverse>, and <sudo coredumpctl --reverse>) -- made immediately upon reboot after a crash -- are no different. <valgrind --log-file=konsole konsole> produces the following (generating the file "konsole"): ==5402== Memcheck, a memory error detector ==5402== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==5402== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info ==5402== Command: konsole ==5402== Parent PID: 4945 ==5402== <coredumpctl gdb 4945> produces: No match found. <valgrind --log-file=kwin kwin> (I tried kwin; Kwin; KWin) produces: valgrind: kwin: command not found -- You are receiving this mail because: You are watching all bug changes.
