thread 'rustc' panicked at 'attempted to read from stolen value',

[samhatchell]

Code

This was short-lived and we couldn't isolate it on a small system.

Meta

rustc --version --verbose:

rustc 1.54.0 (a178d0322 2021-07-26)
binary: rustc
commit-hash: a178d0322ce20e33eac124758e837cbd80a6f633
commit-date: 2021-07-26
host: x86_64-unknown-linux-gnu
release: 1.54.0
LLVM version: 12.0.1

Error output

thread 'rustc' panicked at 'attempted to read from stolen value', /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/compiler/rustc_data_structures/src/steal.rs:37:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.54.0 (a178d0322 2021-07-26) running on x86_64-unknown-linux-gnu

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C linker=clang -C incremental -C link-arg=-fuse-ld=lld --crate-type lib

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [unsafety_check_result] unsafety-checking `RB_NAME`
#1 [analysis] running analysis passes on this crate
end of query stack

Backtrace

This resolved itself before we could get a backtrace.

[kpreid]

Triage: Relabeling issues which don't have a runnable reproduction (as opposed to having a non-minimized one) to the new label S-needs-repro.
@rustbot label +S-needs-repro -E-needs-mcve

[Mark-Simulacrum]

I think we can just close this, I don't see how someone could reproduce this 2+ years down the line.