Description of problem: I was editing some C++ code in VSCode using the official clangd extension for code completion. Version-Release number of selected component: clang-tools-extra-20.1.2-3.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: clangd killed by SIGILL journald_cursor: s=3331c0c5da6a4d3b9af32d20bd6d0365;i=103bca;b=67490499d4244526b355c7ced2758143;m=1b1a0a49c;t=6336e6c7ee569;x=a4a4d9c700b61526 executable: /usr/lib64/llvm20/bin/clangd cmdline: /usr/bin/clangd --compile-commands-dir=/home/rgarcia/devel/vk-gl-cts/build --header-insertion=never cgroup: 0::/user.slice/user-1000.slice/user/app.slice/kitty-6585-1.scope rootdir: / uid: 1000 kernel: 6.14.2-300.fc42.x86_64 package: clang-tools-extra-20.1.2-3.fc42 runlevel: N 5 dso_list: /usr/lib64/llvm20/bin/clangd clang-tools-extra-20.1.2-3.fc42.x86_64 (Fedora Project) 1745227286 backtrace_rating: 4 crash_function: (anonymous namespace)::TemplateArgumentHasher::AddTemplateArgument comment: I was editing some C++ code in VSCode using the official clangd extension for code completion. Truncated backtrace: Thread no. 0 (4 frames) #0 (anonymous namespace)::TemplateArgumentHasher::AddTemplateArgument at /usr/src/debug/llvm-20.1.2-3.fc42.x86_64/clang/lib/Serialization/TemplateArgumentHasher.cpp:68 #1 clang::serialization::StableHashForTemplateArguments at /usr/src/debug/llvm-20.1.2-3.fc42.x86_64/clang/lib/Serialization/TemplateArgumentHasher.cpp:407 #2 clang::ASTReader::LoadExternalSpecializationsImpl at /usr/src/debug/llvm-20.1.2-3.fc42.x86_64/clang/lib/Serialization/ASTReader.cpp:8326 #3 clang::ASTReader::LoadExternalSpecializations at /usr/src/debug/llvm-20.1.2-3.fc42.x86_64/clang/lib/Serialization/ASTReader.cpp:8350
Created attachment 2086624 [details] File: proc_pid_status
Created attachment 2086625 [details] File: maps
Created attachment 2086626 [details] File: limits
Created attachment 2086627 [details] File: environ
Created attachment 2086628 [details] File: open_fds
Created attachment 2086629 [details] File: mountinfo
Created attachment 2086630 [details] File: os_info
Created attachment 2086631 [details] File: cpuinfo
Created attachment 2086632 [details] File: core_backtrace
Created attachment 2086633 [details] File: exploitable
Created attachment 2086634 [details] File: backtrace
I was editing a C++ file using Helix. reporter: libreport-2.17.15 type: CCpp reason: clangd killed by SIGILL journald_cursor: s=36eff30049354c35addc0cb3007bc757;i=4eec4d;b=7faa768257f249819636cdaadc7460ab;m=21432783c;t=6356f7a1f1ee2;x=4efe859683821a46 executable: /usr/lib64/llvm20/bin/clangd cmdline: /usr/bin/clangd cgroup: 0::/user.slice/user-1000.slice/user/app.slice/ptyxis-spawn-f50bcd98-d534-4900-8fdc-f5d8993274aa.scope rootdir: / uid: 1000 kernel: 6.14.6-300.fc42.x86_64 package: clang-tools-extra-20.1.3-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: (anonymous namespace)::TemplateArgumentHasher::AddTemplateArgument comment: I was editing a C++ file using Helix.
Thanks for the report, the backtrace looks exactly like the one in https://bugzilla.redhat.com/show_bug.cgi?id=2363895, unfortunately the author of the offending patch won't have time to look into this problem. *** This bug has been marked as a duplicate of bug 2363895 ***
Thanks for looking into this! As a workaround, I've downloaded the Linux binary release of clangd 19.1.2 from https://github.com/clangd/clangd/releases/tag/19.1.2 and dumped it somewhere in my home directory. The official VSCode clangd plugin allows you to specify the clangd binary path. Version 19.1.2 does not crash, so I can work normally for now.