Rustc reports error on Ctrl-C during linking
Open
Nobody has claimed this yet.
A-linkage
C-bug
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
^C
gh-bjorn3@dev-desktop-eu-1:~/cg_clif$ error: linking with `cc` failed: signal: 2 (SIGINT)
|
= note: LC_ALL="C" PATH="/home/gh-bjorn3/cg_clif/dist/lib/rustlib/aarch64-unknown-linux-gnu/bin:/home/gh-bjorn3/.local/bin:/home/gh-bjorn3/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" VSLANG="1033" "cc" "/tmp/rustc3QDuN1/symbols.o" [...]
= note:
error: aborting due to 1 previous error
Rustc should probably check if it received SIGINT itself and if so ignore child processes exiting with SIGINT.
This is almost certainly a regression from https://github.com/rust-lang/rust/pull/111769
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the regression referenced in Rust pull request #111769, then reproduce the Ctrl-C interruption during linking described in the report. Trace how rustc handles its own SIGINT and the linker’s exit status; done means interrupting a link no longer produces the reported linker error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100