-
Notifications
You must be signed in to change notification settings - Fork 13.5k
LLDB crashes when printing a clang::TemplateDecl
object
#66335
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
Comments
The |
@llvm/issue-subscribers-lldb
LLDB crashed when I tried printing an object while debugging clang++.
Here is the stack trace.
LLDB diagnostics is as follows.
The struct X {
X(const T&);
};
void f() {
auto x = X(42);
} The versions of lldb/clang++ are
GDB prints the object correctly.
|
Doesn't repro for me on my M1 Mac. I'll check on my Linux x86 machine What does your
|
|
Couldn't reproduce on my Ubuntu x86_64 machine either with top-of-tree clang/lldb How are you building clang/lldb? Could you provide your cmake and build invocations please? |
I built lldb by with the following commands (there are unrelated components, but there is a no problem). $ cmake \
-G Ninja \
-DCMAKE_INSTALL_PREFIX=/path/to/install \
-DCMAKE_BUILD_TYPE=Release \
-DLLVM_LINK_LLVM_DYLIB=ON \
-DLLVM_TARGETS_TO_BUILD=host \
-DLLVM_TARGETS_TO_BUILD="X86;AArch64" \
-DLLVM_ENABLE_PROJECTS="clang;flang;mlir;lldb" \
-DLLVM_ENABLE_RUNTIMES="compiler-rt;openmp;libcxx;libcxxabi" \
/path/to/llvm
$ ninja
$ ninja install Then I built clang in debug mode. $ cmake \
-G Ninja \
-DCMAKE_INSTALL_PREFIX=/path/to/install-clang \
-DCMAKE_BUILD_TYPE=Debug \
-DLLVM_LINK_LLVM_DYLIB=ON \
-DLLVM_TARGETS_TO_BUILD=host \
-DLLVM_ENABLE_PROJECTS="clang" \
../../llvm
$ ninja
$ ninja install This is my first time building and using lldb, so I may have made some odd mistakes... |
LLDB crashed when I tried printing an object while debugging clang++.
Here is the stack trace.
LLDB diagnostics is as follows.
The
main.cpp
I passed to clang++ is as follows.The versions of lldb/clang++ are
GDB prints the object correctly.
The text was updated successfully, but these errors were encountered: