Skip to content

clangd crash #117670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Du-Guang-rong opened this issue Nov 26, 2024 · 6 comments
Closed

clangd crash #117670

Du-Guang-rong opened this issue Nov 26, 2024 · 6 comments
Labels
clang-tidy crash Prefer [crash-on-valid] or [crash-on-invalid] duplicate Resolved as duplicate

Comments

@Du-Guang-rong
Copy link

clangd version 19.1.1 (CentOS 19.1.1-5.el10)
Features: linux
Platform: x86_64-unknown-linux-gnu; target=x86_64-redhat-linux-gnu

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
#0 0x00007f24b8438f4a llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/lib64/libLLVM.so.19.1+0x638f4a)
#1 0x00007f24b84363f6 llvm::sys::RunSignalHandlers() (/lib64/libLLVM.so.19.1+0x6363f6)
#2 0x00007f24b843970b (/lib64/libLLVM.so.19.1+0x63970b)
#3 0x00007f24bea69ac0 __restore_rt (/lib64/libc.so.6+0x40ac0)
#4 0x00007f24b83c7ee1 llvm::StringMapImpl::LookupBucketFor(llvm::StringRef, unsigned int) (/lib64/libLLVM.so.19.1+0x5c7ee1)
#5 0x0000561159bb11f6 (/usr/bin/clangd+0x5c21f6)
#6 0x0000561159bafc84 (/usr/bin/clangd+0x5c0c84)
#7 0x000056115a20a78f (/usr/bin/clangd+0xc1b78f)
#8 0x0000561159939837 (/usr/bin/clangd+0x34a837)
#9 0x00005611599d20f8 (/usr/bin/clangd+0x3e30f8)
#10 0x00005611599d1b6a (/usr/bin/clangd+0x3e2b6a)
#11 0x00005611599cd763 (/usr/bin/clangd+0x3de763)
#12 0x00005611599cb83f (/usr/bin/clangd+0x3dc83f)
#13 0x0000561159b45002 (/usr/bin/clangd+0x556002)
#14 0x00007f24beabd9e9 start_thread (/lib64/libc.so.6+0x949e9)
#15 0x00007f24beb2d4bc __GI___clone3 (/lib64/libc.so.6+0x1044bc)
Signalled during AST worker action: Build AST

@EugeneZelenko EugeneZelenko added clangd incomplete Issue not complete (e.g. missing a reproducer, build arguments, etc.) crash Prefer [crash-on-valid] or [crash-on-invalid] and removed new issue labels Nov 26, 2024
@llvmbot
Copy link
Member

llvmbot commented Nov 26, 2024

@llvm/issue-subscribers-clangd

Author: None (Du-Guang-rong)

clangd version 19.1.1 (CentOS 19.1.1-5.el10) Features: linux Platform: x86_64-unknown-linux-gnu; target=x86_64-redhat-linux-gnu

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
#0 0x00007f24b8438f4a llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/lib64/libLLVM.so.19.1+0x638f4a)
#1 0x00007f24b84363f6 llvm::sys::RunSignalHandlers() (/lib64/libLLVM.so.19.1+0x6363f6)
#2 0x00007f24b843970b (/lib64/libLLVM.so.19.1+0x63970b)
#3 0x00007f24bea69ac0 __restore_rt (/lib64/libc.so.6+0x40ac0)
#4 0x00007f24b83c7ee1 llvm::StringMapImpl::LookupBucketFor(llvm::StringRef, unsigned int) (/lib64/libLLVM.so.19.1+0x5c7ee1)
#5 0x0000561159bb11f6 (/usr/bin/clangd+0x5c21f6)
#6 0x0000561159bafc84 (/usr/bin/clangd+0x5c0c84)
#7 0x000056115a20a78f (/usr/bin/clangd+0xc1b78f)
#8 0x0000561159939837 (/usr/bin/clangd+0x34a837)
#9 0x00005611599d20f8 (/usr/bin/clangd+0x3e30f8)
#10 0x00005611599d1b6a (/usr/bin/clangd+0x3e2b6a)
#11 0x00005611599cd763 (/usr/bin/clangd+0x3de763)
#12 0x00005611599cb83f (/usr/bin/clangd+0x3dc83f)
#13 0x0000561159b45002 (/usr/bin/clangd+0x556002)
#14 0x00007f24beabd9e9 start_thread (/lib64/libc.so.6+0x949e9)
#15 0x00007f24beb2d4bc __GI___clone3 (/lib64/libc.so.6+0x1044bc)
Signalled during AST worker action: Build AST

@EugeneZelenko
Copy link
Contributor

@Du-Guang-rong: Could you please provide reproducer?

@HighCommander4
Copy link
Collaborator

Based on the LookupBucketFor in the backtrace, this is almost certainly #109367, a 19.1.0 regression which was fixed in 19.1.2.

@Du-Guang-rong
Copy link
Author

#117670 (comment)

I think you are right, I vi ~/.config/clangd/config.yaml file
and change this line:
boost-*,
to
#boost-*,

then this problem is resolved. crash is NOT found again :)

@HighCommander4
Copy link
Collaborator

Duplicate of #109367

@HighCommander4 HighCommander4 marked this as a duplicate of #109367 Nov 26, 2024
@HighCommander4 HighCommander4 closed this as not planned Won't fix, can't repro, duplicate, stale Nov 26, 2024
@EugeneZelenko EugeneZelenko added duplicate Resolved as duplicate clang-tidy and removed clangd incomplete Issue not complete (e.g. missing a reproducer, build arguments, etc.) labels Nov 26, 2024
@llvmbot
Copy link
Member

llvmbot commented Nov 26, 2024

@llvm/issue-subscribers-clang-tidy

Author: None (Du-Guang-rong)

clangd version 19.1.1 (CentOS 19.1.1-5.el10) Features: linux Platform: x86_64-unknown-linux-gnu; target=x86_64-redhat-linux-gnu

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace.
#0 0x00007f24b8438f4a llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/lib64/libLLVM.so.19.1+0x638f4a)
#1 0x00007f24b84363f6 llvm::sys::RunSignalHandlers() (/lib64/libLLVM.so.19.1+0x6363f6)
#2 0x00007f24b843970b (/lib64/libLLVM.so.19.1+0x63970b)
#3 0x00007f24bea69ac0 __restore_rt (/lib64/libc.so.6+0x40ac0)
#4 0x00007f24b83c7ee1 llvm::StringMapImpl::LookupBucketFor(llvm::StringRef, unsigned int) (/lib64/libLLVM.so.19.1+0x5c7ee1)
#5 0x0000561159bb11f6 (/usr/bin/clangd+0x5c21f6)
#6 0x0000561159bafc84 (/usr/bin/clangd+0x5c0c84)
#7 0x000056115a20a78f (/usr/bin/clangd+0xc1b78f)
#8 0x0000561159939837 (/usr/bin/clangd+0x34a837)
#9 0x00005611599d20f8 (/usr/bin/clangd+0x3e30f8)
#10 0x00005611599d1b6a (/usr/bin/clangd+0x3e2b6a)
#11 0x00005611599cd763 (/usr/bin/clangd+0x3de763)
#12 0x00005611599cb83f (/usr/bin/clangd+0x3dc83f)
#13 0x0000561159b45002 (/usr/bin/clangd+0x556002)
#14 0x00007f24beabd9e9 start_thread (/lib64/libc.so.6+0x949e9)
#15 0x00007f24beb2d4bc __GI___clone3 (/lib64/libc.so.6+0x1044bc)
Signalled during AST worker action: Build AST

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang-tidy crash Prefer [crash-on-valid] or [crash-on-invalid] duplicate Resolved as duplicate
Projects
None yet
Development

No branches or pull requests

4 participants