OS: KDE Neon 22.04
VSCode version: Code insiders 1.80.0-1688469339
CodeLLDB version:
Compiler:
Clang installed in ~/llvm/bin, which is put on the path via ~/.bashrc
Cargo/Rust, with CARGO_HOME and RUSTUP_HOME defined as ~/.cargo and ~/.rustup (defined in ~/.bashrc)
Debuggee: x86_64-linux-gnu
When using the cargo builds from the debugger, the binaries are rebuilt even though they are already built in the terminal.
My speculation is that this is caused by different environments for the terminal and the debugger. It seems that the debugger doesn't use ~/.bashrc even though I launched VsCode from the terminal. I also use .cargo/config.toml to specify some settings.
OS: KDE Neon 22.04 VSCode version: Code insiders 1.80.0-1688469339 CodeLLDB version: Compiler: Clang installed in ~/llvm/bin, which is put on the path via ~/.bashrc Cargo/Rust, with CARGO_HOME and RUSTUP_HOME defined as ~/.cargo and ~/.rustup (defined in ~/.bashrc)
Debuggee: x86_64-linux-gnu
When using the cargo builds from the debugger, the binaries are rebuilt even though they are already built in the terminal.
My speculation is that this is caused by different environments for the terminal and the debugger. It seems that the debugger doesn't use
~/.bashrceven though I launched VsCode from the terminal. I also use.cargo/config.tomlto specify some settings.Related to #791
Verbose log