Remote debugging: No such file or directory #964
Replies: 3 comments 2 replies
-
Try adding 'log enable lldb:all' command for more detailed logging. |
Beta Was this translation helpful? Give feedback.
-
Ok so trying to do the same thing on another machine running Fedora 38 it works fine (as opposed to Ubuntu 20.04.5 where it's failing). |
Beta Was this translation helpful? Give feedback.
-
Do not run lldb-server in the directory of the executable program, because lldb will transfer the executable program to the current directory of lldb-server, and then let lldb-server execute the executable program (because remote debugging is implemented using the client-server architecture). |
Beta Was this translation helpful? Give feedback.
-
OS:
Ubuntu 20.04.5 LTS
VSCode version:
1.79.2
CodeLLDB version:
v1.9.2
Compiler:
Rust
Debuggee:
aarch64-linux-gnu
I'm currently trying to debug an application that is supposed run as root. As vscode run from user mode (to my knowledge) does not offer a way to attach to a binary run as root, I'm doing this by spawning an
lldb-server
as root (sudo lldb-server platform --server --listen localhost:7777
) and then attaching to that server.So to recap I'm trying to attach to an
lldb-server
running on the same machineI'm using the following config based on the one described here
However when launching the debug session in vscode I get
Unfortunately I get no information what the file is that wasn't found. I'm certain that the path to the binary is correct as changing that gives me an entirely different error telling me that the binary wasn't found.
Attaching to the
lldb-server
vialldb
from the command line does work just fine:Verbose log
If there's any further information I can provide, please let me know <3
Beta Was this translation helpful? Give feedback.
All reactions