Unable to start debugging in macOS Big Sur

[sadovsf]

Type: LLDB

Describe the bug

• OS and Version: macOS Big Sur 11.2
• VS Code Version: 1.53.2
• C/C++ Extension Version: 1.2.1, 1.2.2-insiders
• A clear and concise description of what the bug is.
  Last few days (seems that it started to happen after update to 1.2.x version iam no longer able to debug c++. Even stopAtEntry simply does nothing and after i quit exe i lunched through vscode and wanted to debug (no changes in config happened) vscode just stays in debug mode (with little stop, restart, step in etc widget open).

To Reproduce
Just try to start debugging of app using F5, seems that lldb debugger does start (i can see it in system monitor) but vscode never attaches to it or is unable to communicate.

Additional context
log.txt

[sadovsf]

Note that after downgrading plugin to 1.1.3 debugging works again

[sean-mcmanus]

@WardenGnaw Do you have any ideas about this? Debugging is working for me on Big Sur. The only thing that I know changed with 1.2.1 is that we signed the lldb-mi binary.

[WardenGnaw]

From the logs, it looks like it is waiting for the UI to do something.

Nothing in the debug launch has changed between 1.1.3 to 1.2.1. and LLDB-MI has not changed (besides signing) since 0.27.0.

[sadovsf]

Is there something more i can provide to help you identify this issue?

[SRTwILeK]

I have same issue
When I start the debugger I see logs in the debug console and I can debug the application for a short time, and the debugger detach from the application and exit with error code: 137
Same issue on Catalina and Big Sur
I revert back the vs-cpptools to 1.2.0 and it works again, so the issue is in the 1.2.1 version

[SRTwILeK]

1: (45289) "/Users/macuser/.vscode/extensions/ms-vscode.cpptools-1.2.2-insiders2/debugAdapters/lldb-mi/bin/lldb-mi" exited with code 137 (0x89).
1: (45290) <-logout
1: (45299) Send Event AD7MessageEvent
ERROR: LLDB exited unexpectedly with exit code 137 (0x89). Debugging will now abort.

Same error with version 1.2.1
(catalina and big sur)
Version: 1.53.2
Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4
Date: 2021-02-11T11:45:54.515Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.2.0

[sadovsf]

I can confirm that i have seen this exit and 137 error right after debugging start as well. Or better say, this was in log. Then exe started. vscode was showing it is debugging but no debug output or breakpoints worked

[sadovsf]

I can confirm issue persist in 1.2.2

[feuerste]

Same issue with 1.3.0-insiders5

[feuerste]

Wow, interesting, I rebooted my mac, now it works.

[sadovsf]

I tried rebooting both right after updating without starting vscode and after vscode downloaded new version of lldb-mi. In both case after reboot debugging was still not working.

After second reboot console reported lldb error 137 and claimed that binary exited with code -1 (0xffffffff) although it did not and i actually run binary no problem. Almost seems like lldb runed into some error and just somehow force disconnected from binary itself.

I was trying version 1.2.2 so for me issue persists

[sadovsf]

And today same confirmed on newest 1.3.0

[sadovsf]

So in case someone is strugling with same issue i managed to "fix" it by using different lldb debugger plugin named CodeLLDB which works no problem and for stepping through code is actually insanely faster for my big project for some reason. I will occasionally try this in case it will be resolved but until then CodeLLDB seems to be my only help :-(

[nazavode]

Same here. Exiting VSCode leaves the lldb-mi process alive. Version 1.4.0 on Big Sur 11.3.1.