cargo-bins/cargo-debug

Debug subcommand for cargo

cargo-debug's Issues

Debugging the build script

Currently, my cargo build fails due to the build-script crashes. I would like to start the debugger to investigate where the build-script crashes, but cargo-debug doesn't start:

% cargo debug build
args: ["/home/joerg/.cargo/bin/cargo-debug", "debug", "build"]
   Compiling website v0.0.0 (/home/joerg/Projekte/daheme/website)
error: could not compile `website` due to 9 previous errors
thread 'main' panicked at 'no viable output artifacts found', /home/joerg/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-debug-0.3.0/src/main.rs:166:28
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I have to manually run gdb ../target/debug/build/website-e333b96705e42304/build-script-build

cargo-debug 0.3.0

Can't parse `debug=1` in cargo.toml

My cargo.toml contains the following, which causes cargo-debug to break

[profile.release]
debug = 1

(this is OK according to the docs: https://doc.rust-lang.org/cargo/reference/profiles.html#debug)

Be more compatable with run?

It would be nice (for me at least) if debug tried to be a drop-in replacement for run, so I can easily switch between the two.

For example, with run I would normally do:

cargo run --bin myprog -- args

but cargo debug doesn't accept "--bin".

Fails to start in subdirectory

Would it be possible to enhance cargo-debug to run from a subdirectory and not only where Cargo.toml lives? Currently, I'm getting

% cargo debug build
args: ["/home/joerg/.cargo/bin/cargo-debug", "debug", "build"]
thread 'main' panicked at 'Failed to read Cargo.toml: CargoTomlError { inner: Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }) }', /home/joerg/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-debug-0.3.0/src/main.rs:95:51
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

cargo-debug 0.3.0

The author is required by cargo-debug

It gets an error on start, if authors is not specified.
Adding authors solved the problem.