Closed PaulGrandperrin closed 3 years ago
@PaulGrandperrin
This is a transient (not sure if it's the correct word) bug.
I think you may have meant "spurious"?
Also, can you check if you can reproduce this issue on stable? Or, if you are using nightly features, can you check if it works on an older nightly? Thanks!
Running
cargo clean
and thencargo run
works fine.
This makes me think it might be an incr-comp metadata bug, so tagging as such.
I think you may have meant "spurious"?
that's it!
Also, can you check if you can reproduce this issue on stable? Or, if you are using nightly features, can you check if it works on an older nightly? Thanks!
Unfortunately, I really haven't found a way to reproduce from a clean state.. Which is why, when I got the ICE, I precautiously saved all compiler artifacts before touching anything (it's not the first time I hit that kind of bug, so now I know what to do ;-) )
Yeah, unfortunately metadata/incr-comp bugs tend to be very hard to reproduce :/
FYI: I just triggered this too on nightly: (new to rust - apologies if I miss some critical context):
robs@grr:~/git/ned_d_bug/html$ rustup show Default host: x86_64-apple-darwin rustup home: /Users/robs/.rustup
stable-x86_64-apple-darwin nightly-x86_64-apple-darwin (default)
nightly-x86_64-apple-darwin (default) rustc 1.50.0-nightly (1700ca07c 2020-12-08)
thread 'rustc' panicked at 'called Option::unwrap()
on a None
value', compiler/rustc_metadata/src/rmeta/decoder.rs:1565:75
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::panicking::panic
3: core::lazy::OnceCellRUST_BACKTRACE=full
for a verbose 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.50.0-nightly (1700ca07c 2020-12-08) running on x86_64-apple-darwin
note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental --crate-type bin
note: some of the compiler flags provided by cargo are hidden
--- let me know if I can provide any more info and thanks for such a great language!
@robs-zeynet At this point the most helpful information would be a small example that reproduces the crash and doesn’t depend on external libraries. If your code is small and you can share it, that would be great!
I suspect that this is a duplicate of https://github.com/rust-lang/rust/issues/79783, and will be fixed by https://github.com/rust-lang/rust/pull/79810
Closing as a duplicate of #79783. Of course reopen if the fix for that one doesn't fix your issue!
This is a transient (not sure if it's the correct word) bug. The code was compiling fine, then I changed the port number of the server ("8081" to "8080"), tried to compile again and got this ICE.
Running
cargo clean
and thencargo run
works fine.Nothing special happened in between as far I as know (no toolchain upgrade for instance..)
I made a
tar
of the full directory at the time of the bug to keep all the compiler artifacts intact. If needed, don't hesitate to ask me for it :-)Code
Meta
rustc --version --verbose
:Error output