Closed zakalawe closed 1 year ago
Forgot to add : when LLDb exists, the debugged process carries on running as normal, i.e my application is not crashing or existing, LLDB-mi is detaching I guess.
Can I tell cpptools to use the system lldb-mi, and see if that works? Or does cpptools need its custom lldb-mi binary for some reason?
If you have a system lldb-mi
, feel free to use it.
LLVM has stopped shipping lldb-mi
after 10.x so cpptools ships a lldb-mi
for customers who do not have a system one.
LLVM only ships lldb
and they are building lldb-vscode
at https://github.com/llvm/llvm-project/tree/main/lldb/tools/lldb-vscode
If you know where it is, you can point to it with miDebuggerPath
in your launch.json
As for the crash, it seems like lldb-mi is crashing and the lldb-mi owners would have to investigate why its crashing.
I understood a bit more what's happening on my system: I have the Homebrew 'llvm' package installed, which includes its own lldb-mi
binary. For a workaround I can use that, but I guess I need to report the lldb-mi bug upstream somewhere, so that a future version of cpptools
can use it with my crash fixed.
Environment
From my Apple/ XCode lldb, it's
11:33 $ lldb --version lldb-1300.0.42.3 Swift version 5.5.2-dev
Bug Summary and Steps to Reproduce
Bug Summary:
When starting to debug my application, the lldb-mi shipped with CppTools immediately exits:
When I use the system 'lldb' on the same binary, debugging works as expected.
Debugger Configurations