VSCode debug extension for probe-rs. It uses the MS DAP protocol to communicate directly with the probe (via probe-rs), and supports basic command line debugging in addition to VSCode UI.
I'm trying to setup debugging with a remote probe (via SSH tunnel); I have a probe-rs DAP server running on my remote host, and a VS Code instance on my local machine. While adjusting the launch options, I realized that probe-rs tries to find the programBinary on the remote host, rather than in my local repository.
If I copy program.elf to the remote host, the debug session starts successfully. The same issue may apply to svdFile, although I am unable to test this currently.
It would be helpful if there was an option (or the default behaviour) to automatically upload and use the local program binary from VS Code.
@calebchalmers A similar request has been opened on the repo that hosts the dap server behind this extension. I'm linking it here to keep the two connected :)
I'm trying to setup debugging with a remote probe (via SSH tunnel); I have a probe-rs DAP server running on my remote host, and a VS Code instance on my local machine. While adjusting the launch options, I realized that
probe-rs
tries to find theprogramBinary
on the remote host, rather than in my local repository.If I copy
program.elf
to the remote host, the debug session starts successfully. The same issue may apply tosvdFile
, although I am unable to test this currently.It would be helpful if there was an option (or the default behaviour) to automatically upload and use the local program binary from VS Code.
Log:
Launch configuration: