-
Notifications
You must be signed in to change notification settings - Fork 13.7k
Not planned
Labels
A-incr-compArea: Incremental compilationArea: Incremental compilationA-linkageArea: linking into static, shared libraries and binariesArea: linking into static, shared libraries and binariesC-bugCategory: This is a bug.Category: This is a bug.
Description
When interrupting linking with rust-lld.exe it sometimes corrupts the target and the only recovery is cargo clean
.
I'm getting tones of errors like this if I try cargo build
again after:
= note: rust-lld: error: undefined symbol: anon.8ff5a01038e5b419b80b5d238bffa21c.22.llvm.13741956020784447919
rust-lld: error: undefined symbol: xx::xxxx::xxxx::GLOBAL::h22b2a472d7972d2f (.llvm.10192556018238492745)
rust-lld: error: undefined symbol: core::hint::unreachable_unchecked::precondition_check::h644ec5c1a75164f9 (.llvm.10192556018238492745)
This isn't a good UX. Ctrl+C should be robust and not leave things in a bad state.
Metadata
Metadata
Assignees
Labels
A-incr-compArea: Incremental compilationArea: Incremental compilationA-linkageArea: linking into static, shared libraries and binariesArea: linking into static, shared libraries and binariesC-bugCategory: This is a bug.Category: This is a bug.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
[-]rust-lld corruption with Cltr+C[/-][+]rust-lld corruption with Ctrl+C[/+]bjorn3 commentedon Aug 9, 2024
Duplicate of #81280. Recovering from this can also be done by clearing the incr comp cache using
rm -r target/debug/incremental
. The incr comp cache should only be finalized after it is fully written, but this bug seems to indicate that finalization of the incr comp cache is done just a bit too early.workingjubilee commentedon Aug 10, 2024
closing as duplicate.