Open ohmtech-rdi opened 1 year ago
Copying
/Users/***/.vscode/extensions/ms-vscode.cpptools-1.15.4-darwin-x64/debugAdapters/lldb-mi/bin/lldb-mi
to my
/Applications/Xcode113.app/Contents/SharedFrameworks/
and then referencing it in the launch configuration:
"osx": {
"MIMode": "lldb",
"program": "/Applications/VCV Rack 2 Pro.app/Contents/MacOS/Rack",
"miDebuggerPath": "/Applications/Xcode113.app/Contents/SharedFrameworks/lldb-mi"
}
Makes debugging possible, so it seems to be clearly related to that.
Note that my Xcode doesn't have a standard name, if the extension used a hardcoded path to Xcode.app
.
Yet:
$ xcode-select -p
/Applications/Xcode113.app/Contents/Developer
All in all, debugging on VSCode will require LLDB.framework
from Xcode, so I'm wondering if we should put it as part of our toolchain?
Another option would be to not rely on our make
configuration and instead go for the most vanilla project on VS Code for C++? It is not clear if the workaround above is not required anyway.
Tested on macOS 10.15, Xcode 11.3 is installed.
Could be related to the absence of
lldb-mi
. Maybe more informations here. If this is the case, we could include it to our toolchain.