Open tfar opened 4 years ago
The miDebuggerPath
requires the debugger to have a machine interface (MI). lldb
itself does not support a MI Mode, you will need to point miDebuggerPath to lldb-mi
.
LLVM has removed lldb-mi from its toolchain and XCode does not ship it anymore. So for macOS Catalina, the cpptools extension ships its own version of lldb-mi
, you can exclude miDebuggerPath
from your launch.json
and we will auto-resolve that path.
Alright. I've removed the miDebuggerPath
, with my launch.json
now looking like:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "(lldb) Launch",
"type": "cppdbg",
"request": "launch",
"program": "${workspaceFolder}/QA/UnitTest/checker",
"args": [],
"stopAtEntry": false,
"cwd": "${workspaceFolder}",
"environment": [],
"externalConsole": false,
"MIMode": "lldb"
}
]
}
Now I see the following in the logs when I hit the debug button:
[23727:0625/222039.646499:INFO:CONSOLE(1670)] "%cTRACE color: #888 [text file model] load() - enter file:///Users/tobias/Development/swift-public/Swiften/Client/BlockList.cpp", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[main 2020-06-25T20:20:39.885Z] menubarService#updateMenubar 1
[23727:0625/222040.741562:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent: onDebug", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[23727:0625/222040.746952:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent: onDebugResolve", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[23727:0625/222040.747922:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent: onDebug", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[23727:0625/222040.771155:INFO:CONSOLE(1670)] "%cTRACE color: #888 onWillActivateByEvent: onDebug", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
[main 2020-06-25T20:20:41.027Z] menubarService#updateMenubar 1
[23727:0625/222042.223168:INFO:CONSOLE(1670)] "%c ERR color: #f33 timeout after 1000 ms: Error: timeout after 1000 ms
at t.RawDebugSession.handleErrorResponse (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3160:190)
at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3159:451
at async t.RawDebugSession.shutdown (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3157:536)", source: file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js (1670)
Which looks pretty much the same as before.
Can you share the logs from the debug console
? engineLogs will be printed there.
The logs from debug console
are empty. In the output
tab right next to it, there is no entry for C/C++ logs either. 🤷
@WardenGnaw Any idea how to get down to the issue of missing debug console
?
From the empty debug console
it seems like VS Code isnt calling our debug adapter at all. This may be a weird state that may require you to reinstall VS Code and the extension.
Just to check, dDo you have lldb-mi in ~/.vscode/extensions/ms.vscode-cpptools-0.28.3/debugAdapters/lldb-mi
, and if so, can it run in the commandline?
Yes. Running that works and answers like:
~> ~/.vscode/extensions/ms-vscode.cpptools-0.28.3/debugAdapters/lldb-mi/bin/lldb-mi
(gdb)
Type: Debugger
Describe the bug
Additional context My
launch.json
contents:Output of
code --log trace --verbose
when hitting the debug button: