CodeLLDB cannot find "cargo" executable

[dotmatrixbeeper]

OS: Ubuntu 24.04
Editor: VSCode
CodeLLDB: 1.11.6

I have the following project structure

advent-of-code-rust
    +---y2015
        +---day1
        |   +-- src
        |   +-- Cargo.toml
        +---day2
        |   +-- src
        |   +-- Cargo.toml
        +---Cargo.toml // workspace toml

with advent-of-code-rust being the current working directory.

I have the following launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Debug day17",
            "program": "${workspaceFolder}/y2015/target/debug/day17",
            "cargo": {
                "args": [
                    "build",
                    "--package",
                    "day17"
                ],
                "cwd": "${workspaceFolder}/y2015"
            },
            "cwd": "${workspaceFolder}",
            "args": []
        }
    ]
}

When I try to run Debug day17 to start debugging I get the following error
`Cargo: could not find "cargo" executable.

with the LLDB output as

Verbose logging: on  (Use "lldb.verboseLogging" setting to change)
Platform: linux x64
Initial debug configuration: {
  type: 'lldb',
  request: 'launch',
  name: 'Debug day17',
  program: '${workspaceFolder}/y2015/target/debug/day17',
  cargo: {
    args: [ 'build', '--package', 'day17' ],
    cwd: '${workspaceFolder}/y2015'
  },
  cwd: '${workspaceFolder}',
  args: [],
  __configurationTarget: 6
}
Running: cargo build --package day17 --message-format=json --color=always --config=target.'cfg(all())'.runner='/home/hereiskkb/.vscode/extensions/vadimcn.vscode-lldb-1.11.6/adapter/codelldb-launch'
Cargo: could not find "cargo" executable.

As far as I can understand this would indicate that Cargo executable is not being found by LLDB. I have tried providing PATH to cargo in "env" in launch.json as well. But nothing seems to work. I am not sure what the configuration needs to be for this to work. Can someone please help me out with this?

[vadimcn]

What happens if you run cargo in vscode terminal? It needs to be on PATH in which VSCode sees.
You should be able to specify the full path via lldb.cargo setting.

[dotmatrixbeeper]

cargo in vscode terminal works normally showing all the help commands.
I have tried appedning cargo path to env in lldb.cargo as well as outside it like:

"env": {
    "PATH": "${env:HOME}/.cargo/bin:${env:PATH}"
 }

still doesn't work. (Same result - Cargo: could not find "cargo" executable)

I have tried providing the relativePathBase to be alternatively the path to workspace as well as the particular crate inside workspace. Same results.

The only way I have gotten this to work (somewhat) is by creating a new vscode workspace, adding y2015, y2016 etc. cargo workspace folders to the vscode workspace. And then generating launch.json for crates within the cargo workspaces, in which case there is a launch.json created for each of the workspaces.

My original intention was to see if I can have one launch.json at the top level folder (advent-of-code-rust) to be able to control my test cases by only modifying this launch config as required. However, it currently does not work if the containing folder does not have a Cargo.toml.

[vadimcn]

I was talking about adding "lldb.cargo": "/home/user/.cargo/bin/cargo" to your settings.json.
Not sure what's going on with your PATH...

[dotmatrixbeeper]

It goes: Cargo: could not find "/home/user/.cargo/bin/cargo" executable.
Again, cargo runs normally when run from the vscode terminal, or any other place really.
Just do not understand why it refuses to start in the lldb context.

[vadimcn]

/home/user/.cargo/bin/cargo was an example. Did you replace that with the actual cargo binary path?

[dotmatrixbeeper]

Yeah. I replaced it with the actual binary path

holllywood@pop-os:~$ which cargo
/home/holllywood/.cargo/bin/cargo