thread 'rustc' panicked at 'Box<Any>'

[maalgorium]

Hi. I was building Redox and ran into an issue. Searched around but didn't find a duplicate so here it is. (Minor note: the compiler asks you to enable RUST_BACKTRACE even when it is already enabled.)

MacOS 10.11.4
rustc 1.10.0-nightly (2174bd9 2016-04-14)

RUST_BACKTRACE=1 rustc --target=i386-unknown-redox.json -L build/i386-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=2 -Z no-landing-pads -A dead_code -C ar=i386-elf-ar -C linker=i386-elf-gcc -C lto -o build/i386-unknown-redox/debug/kernel.rlib kernel/main.rs
error: internal compiler error: ../src/librustc_metadata/encoder.rs:218: encode_symbol: id not found 2394
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'Box<Any>', ../src/libsyntax/errors/mod.rs:575
stack backtrace:
   1:        0x110d7d508 - std::sys::backtrace::tracing::imp::write::h9fb600083204ae7f
   2:        0x110d89955 - std::panicking::default_hook::_$u7b$$u7b$closure$u7d$$u7d$::hca543c34f11229ac
   3:        0x110d8948f - std::panicking::default_hook::hc2c969e7453d080c
   4:        0x110d4e0e6 - std::sys_common::unwind::begin_unwind_inner::h30e12d15ce2b2e25
   5:        0x11032e91a - std::sys_common::unwind::begin_unwind::h24c4c0fa2cfe995a
   6:        0x11032e749 - syntax::errors::Handler::bug::h9033aa2bf9160334
   7:        0x10f6bb8ac - rustc::session::opt_span_bug_fmt::_$u7b$$u7b$closure$u7d$$u7d$::hf0fb5697f8f25f40
   8:        0x10f6bb711 - rustc::session::opt_span_bug_fmt::hc581ba88c4e2ec53
   9:        0x10f6d1f89 - rustc::session::bug_fmt::had96c08cb43bd8a1
  10:        0x10c99cc40 - rustc_metadata::encoder::encode_symbol::h3b1cb37a626e1c04
  11:        0x10c9a8773 - rustc_metadata::encoder::encode_info_for_item::h314709c2abbb091f
  12:        0x10c9b89cd - rustc_metadata::encoder::encode_metadata_inner::h09e37c37c8e6a30a
  13:        0x10c9b4589 - rustc_metadata::encoder::encode_metadata::h4e36b53c4c104a33
  14:        0x10ca0f09f - rustc_metadata::csearch::_<impl rustc..middle..cstore..CrateStore<'tcx> for cstore..CStore>::encode_metadata::hccf7a1cd13503a83
  15:        0x10cda6152 - rustc_trans::base::trans_crate::_$u7b$$u7b$closure$u7d$$u7d$::hce620d9b52bd0a30
  16:        0x10cd98f0d - rustc_trans::base::trans_crate::h6ed1dbd6e572a8c2
  17:        0x10c41d3ba - rustc_driver::driver::phase_4_translate_to_llvm::hd7579aae98641824
  18:        0x10c41bb2c - rustc_driver::driver::compile_input::_$u7b$$u7b$closure$u7d$$u7d$::h5534474dbe9371c4
  19:        0x10c4184bd - rustc_driver::driver::phase_3_run_analysis_passes::_$u7b$$u7b$closure$u7d$$u7d$::h5a042a091cd7658c
  20:        0x10c412075 - rustc::ty::context::TyCtxt::create_and_enter::h3f9051bcccbd93e4
  21:        0x10c40ea7c - rustc_driver::driver::phase_3_run_analysis_passes::h9c723484c588a35b
  22:        0x10c3e26c1 - rustc_driver::driver::compile_input::h0629572e6f316b31
  23:        0x10c3c8eef - rustc_driver::run_compiler::h8902aebf8b1849a8
  24:        0x10c3c6282 - std::sys_common::unwind::try::try_fn::h4c74456035d0fcc7
  25:        0x110d7ac9b - __rust_try
  26:        0x110d7ac23 - std::sys_common::unwind::inner_try::h47a4d9cd4a369dcd
  27:        0x10c3c6b19 - _<F as std..boxed..FnBox<A>>::call_box::h27f542a39f1d61ef
  28:        0x110d88828 - std::sys::thread::Thread::new::thread_start::h6f266e069bf4ec2b
  29:     0x7fff8dbaf99c - _pthread_body
  30:     0x7fff8dbaf919 - _pthread_start

make: *** [build/i386-unknown-redox/debug/kernel.rlib] Error 101

[mattico]

See issue here: #32783 seems similar to the second BT posted there.

[crazymykl]

I had had this issue with rustc 1.10.0-nightly (2174bd97c 2016-04-14), but it's gone with rustc 1.10.0-nightly (ed7c56796 2016-04-17).

[Mark-Simulacrum]

The previous comment reports that this issue has been resolved, so closing.