Debugging the build script

[jo-so]

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

[ryankurte]

oooh, if we can pull the build script asset name somehow (it looks like it should be exposed via cargo_metadata in the same way we grab binary names) this would be an excellent feature~!