How can I write my launch.json so the application is closed on Restart Debugging?

[douglaslassance]

Currently, Visual Studio Code shows a little popup when I Restart Debugging:

The task 'CodeLLDB: cargo (bevy-game-jam)' is already active.

Either choice Terminate Task or Restart Task will not terminate the existing instance of the application, resulting in opening a second window.

Here is my launch.json for reference:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Debug executable 'bevy-game-jam'",
            "cargo": {
                "args": ["run"],
                "filter": {
                    "name": "bevy-game-jam",
                    "kind": "bin"
                }
            },
            "args": [],
            "cwd": "${workspaceFolder}"
        }
    ]
}

I tried to write a cross-platform kill preLaunchTask, but not luck.
Thanks in advance for the help.

[vadimcn]

First of all, "cargo" doesn't work that way: you should use it to build your binary, not run it. The debugger has to handle the launch. Try
"cargo": { "args": [ "build", ... }

But aside from that, if you want to execute a task after debugging, VSCode has postDebugTask for that.
Also, CodeLLDB itself supports a bunch of command sequences, which are executed at various points in the debugging session. Note, though, that these are LLDB commands, not VSCode tasks.

[douglaslassance]

I might need a little more hand holding on this one. Using build instead of run is not quite working. I also took a look at what RustRover does when debugging, and it calls $HOME/.cargo/bin/cargo.exe run --color=always --package bevy-game-jam --bin bevy-game-jam --profile dev which builds and attaches to the process properly.

[vadimcn]

I am guessing that RustRover uses a different method for debug launching. Are they somehow intercepting cargo run?
For CodeLLDB, you use cargo to build the binary, then CodeLLDB figures out where the output is, and launches it.