Open DavidMSCode opened 11 months ago
+1
Alright so after messing with this over multiple attempts I found that the workaround in #456 works but you have to be mindful of the fact that vscode-server keeps a separate extensions folder.
So steps to solve for remote debugging:
While this workaround does work it also indicates that for some reason the debugserver that comes with the current version of codelldb is requiring interactive authentication even though developer mode is on and the user is in the _developer group.
OS: Mac OS Sonoma VSCode version: 1.85.1 CodeLLDB version: 1.10, 1.9.2, 1.9.1 Compiler: clang Debuggee: arm64-apple-darwin
When connecting to the vscode server on my mac over ssh (from a windows client) and trying to debug using the lldb launch config, I receive an error where it seems to be saying that I don't have permission to debug. When running vscode locally on the same mac under the same user I do not have this issue. in addition I only recieve this message on 1.9.x. On 1.10 the debug session just loads forever on the windows client and an error is never received. But checking the logs I see a similar inability to attach.
LLDB Output
Checking the mac system logs I can see that debugserver is trying to attach to the PID for the program, but ultimately fails, repeats 10 times and gives up.
Console Log
This does not occur when debugging on the machine locally. Using the default vscode c++ debugger works locally and remotely (well, it attaches, the default debugger still has its own set of issues which is why I've been using codeLLDB). I've attempted common troubleshooting suggestions like deleting the debugserver binary bundled with code lldb, making sure I'm in developer mode and adding the _developer group to my user account to no avail. I upgraded to Sonoma last week but this issue has only started occurring today. As far as I can tell I haven't seen anyone run into this permissions issue over just SSH. "this is a non-interactive debug session, cannot get permission to debug processes." only brings up some xcode issues for debugging locally.
Verbose LLDB Output