Debugging with remote DAP server uses server-side binaries

[calebchalmers]

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.

Log:

probe-rs-debug: Starting debug session from: 127.0.0.1:37940
Invalid program binary file specified '/home/remote/program.elf'

Launch configuration:

{
  "type": "probe-rs-debug",
  "request": "launch",
  "name": "probe_rs",
  "server": "127.0.0.1:7184",
  "cwd": "${workspaceFolder}",
  "chip": "STM32F407IGHx",
  "coreConfigs": [
    {
      "coreIndex": 0,
      "programBinary": "program.elf",
    }
  ]
},

[noppej]

@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 :)

https://github.com/probe-rs/probe-rs/issues/1559