[new feature] add a `Cargo test` debug configuration

While it’s somehow possible to work this around, there should be a simple option to run cargo test in a debugging session.

The way I currently do it is:

• run cargo test in a shell
• take note of the (random) executable name generated by cargo in the target directory
• create a new debug profile using the executable above rather than the default executable name

This is error prone as you have to remember to change the debug profile when the test executable name changes (otherwise gdb will load a binary which is out of sync with the source code)

The way it should be is:

• create a new cargo test profile
• choose the project in the created profile
• profit!

This may actually require changes in Cargo to set/get the temp il

[norru]

Solution 1) works (needs some Json parsing)

norru@GBWWSRUNUBWS02:~/Projects/itadinanta/rust-oids$ cargo test --no-run --message-format=json 2>/dev/null | jq --raw-output -M ".executable" | grep -v null

/home/norru/Projects/itadinanta/rust-oids/target/debug/rust_oids-d9c4a6ba4677afc4

[norru]

@mickaelistria good find. I think there is a solution for us which requires no changes in Cargo.

@gbutler69 if we want to attempt to implement a profile, think there is a solution there: In the link to https://github.com/rust-lang/cargo/issues/1924 @mickaelistria provided:

cargo test --no-run --message-format=json produces a list just built binaries in JSON format.

We can run this as the preliminary build step, parse the output (this is the bit we need implementation for), somehow filter the list to match the correct executable and then feed the result to gdb in the usual way.

Nevertheless, I will give hacking cargo-test a go just to see how hard it is.