https://bugs.kde.org/show_bug.cgi?id=486932
--- Comment #6 from Igor Kushnir <igor...@gmail.com> --- My previous comment missed preliminary coredumpctl steps: 0.1. coredumpctl list kdevelop --since 2024-05-19. 0.2. Locate the necessary entry in the printed table and show its details via `coredumpctl info 151255` (where 151255 is the PID of the entry). 0.3. Find the Storage line in the info output, e.g. "Storage: /var/lib/systemd/coredump/core.kdevelop.1000.df23a15637fe47fbae399826251ac233.151255.1716133189000000.zst (present)" and extract the .zst archive to obtain the actual debuggable core dump file. Oh, and after these steps KDevelop's Frame Stack tool view also shows the backtrace with debug symbols. libclang headers can be opened and examined from the IDE right away. To examine libclang source files as well: 8. Download clang sources. I got the clang repository already, so just `git fetch origin` and `git checkout llvmorg-17.0.6` to match my system clang package version. 9. In the GDB tool view: set substitute-path /usr/src/debug/clang/clang-17.0.6.src /path/to/llvm-project/clang 10. Activate the Frame Stack tool view and switch to another thread, then back, to open libclang source files by clicking their lines in the backtrace. -- You are receiving this mail because: You are watching all bug changes.
