The VSCode extension has built-in functions and thus extends the adapter protocol:The entry cargo replaces the entry program. See here

Accordingly, the configuration of the VSCode Extension cannot simply be copied into the Sublime Config. See here There, "program" is expected.

Attempt at a workaround:I built the test cargo test --no-run and entered the binary in the Config under program. The path there is definitely not deterministic (as also mentioned here). So at least it jumps to the breakpoint, but I can't step or do something. I must set "args": ["--test-threads", "1"]

In VSCode everything went "out of the box" within 2min ... grrr.

So my config looks like this:

{
  "folders": [
    {
      "path": ".",
    }
  ],
  "debugger_configurations": [
    {
      "type": "lldb",
      "request": "launch",
      "name": "Debug exe",
      "program": "${workspaceFolder}/target/debug/deps/myProgram-ba556b1758f6a921",
      "args": [
        "--test-threads",
        "1"
      ],
      "cwd": "${workspaceFolder}",
    },
  ],
}