Last active
June 28, 2019 18:44
-
-
Save pvdrz/4287862a77a35bf8ca84a6c7129d6295 to your computer and use it in GitHub Desktop.
rustc backtrace
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
------------------------------------------ | |
stderr: | |
------------------------------------------ | |
thread 'rustc' panicked at 'assertion failed: `(left == right)` | |
left: `Size { raw: 2 }`, | |
right: `Size { raw: 8 }`', src/librustc/mir/interpret/value.rs:367:17 | |
stack backtrace: | |
0: std::sys_common::backtrace::print | |
1: std::panicking::default_hook::{{closure}} | |
2: std::panicking::default_hook | |
3: rustc::util::common::panic_hook | |
4: std::panicking::rust_panic_with_hook | |
5: std::panicking::continue_panic_fmt | |
6: std::panicking::begin_panic_fmt | |
7: rustc::mir::interpret::value::Scalar<Tag>::to_bits_or_ptr | |
8: rustc_mir::interpret::cast::<impl rustc_mir::interpret::eval_context::InterpretCx<M>>::cast | |
9: rustc_mir::transform::const_prop::ConstPropagator::const_prop | |
10: <rustc_mir::transform::const_prop::ConstPropagator as rustc::mir::visit::MutVisitor>::visit_statement | |
11: <rustc_mir::transform::const_prop::ConstProp as rustc_mir::transform::MirPass>::run_pass | |
12: rustc_mir::transform::run_passes::{{closure}} | |
13: rustc_mir::transform::run_passes | |
14: rustc_mir::transform::optimized_mir | |
15: rustc::ty::query::<impl rustc::ty::query::config::QueryAccessors for rustc::ty::query::queries::optimized_mir>::compute | |
16: rustc::dep_graph::graph::DepGraph::with_task_impl | |
17: rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query | |
18: rustc_mir::monomorphize::collector::collect_items_rec | |
19: rustc_mir::monomorphize::collector::collect_crate_mono_items::{{closure}} | |
20: rustc::util::common::time | |
21: rustc_mir::monomorphize::collector::collect_crate_mono_items | |
22: rustc::util::common::time | |
23: rustc_mir::monomorphize::partitioning::collect_and_partition_mono_items | |
24: rustc::ty::query::__query_compute::collect_and_partition_mono_items | |
25: rustc::ty::query::<impl rustc::ty::query::config::QueryAccessors for rustc::ty::query::queries::collect_and_partition_mono_items>::compute | |
26: rustc::dep_graph::graph::DepGraph::with_task_impl | |
27: rustc::ty::query::plumbing::<impl rustc::ty::context::TyCtxt>::get_query | |
28: rustc_codegen_ssa::base::codegen_crate | |
29: <rustc_codegen_llvm::LlvmCodegenBackend as rustc_codegen_utils::codegen_backend::CodegenBackend>::codegen_crate | |
30: rustc::util::common::time | |
31: rustc_interface::passes::start_codegen | |
32: rustc::ty::context::tls::enter_global | |
33: rustc_interface::passes::BoxedGlobalCtxt::access::{{closure}} | |
34: rustc_interface::passes::create_global_ctxt::{{closure}} | |
35: rustc_interface::passes::BoxedGlobalCtxt::enter | |
36: rustc_interface::queries::Query<T>::compute | |
37: rustc_interface::queries::<impl rustc_interface::interface::Compiler>::ongoing_codegen | |
38: rustc_interface::interface::run_compiler_in_existing_thread_pool | |
39: std::thread::local::LocalKey<T>::with | |
40: scoped_tls::ScopedKey<T>::set | |
41: syntax::with_globals | |
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. | |
query stack during panic: | |
#0 [optimized_mir] processing `main` | |
#1 [collect_and_partition_mono_items] collect_and_partition_mono_items | |
end of query stack | |
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/blob/master/CONTRIBUTING.md#bug-reports | |
note: rustc 1.37.0-dev running on x86_64-apple-darwin | |
note: compiler flags: -Z threads=1 -Z ui-testing -Z unstable-options -C prefer-dynamic -C rpath -C debuginfo=0 | |
------------------------------------------ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment