y.sh cargo run swallows the signal emitted by the running process

[antoyo]

For instance, if the process segfaults, ./y.sh cargo run will not emit a SIGSEGV signal while it should do that.

[GuillaumeGomez]

I don't think signals should be emitted by the parent as well (in this case, SIGSEGV tells that a memory access was wrong, which is only the case of the child, not the parent). We should display which signal ended the process though if any.

[antoyo]

cargo does it, so I believe we should do the same.

[bjorn3]

On Unix you could exec cargo instead of spawning it as subprocess. That is what cargo-clif and rustc-clif do.