Skip to content

caller_location ICEs in Miri #73272

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
RalfJung opened this issue Jun 12, 2020 · 2 comments · Fixed by #73277
Closed

caller_location ICEs in Miri #73272

RalfJung opened this issue Jun 12, 2020 · 2 comments · Fixed by #73277
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-miri Area: The miri tool C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@RalfJung
Copy link
Member

Some Miri tests, e.g. ./miri run tests/run-pass/panic/catch_panic.rs, now ICE with

thread 'rustc' panicked at 'internal error: entered unreachable code', /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/libstd/macros.rs:13:23
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.heygears.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.heygears.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1076
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1537
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:198
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:218
  10: rustc_driver::report_ice
  11: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:481
  12: std::panicking::begin_panic
             at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/libstd/panicking.rs:404
  13: rustc_mir::interpret::intrinsics::caller_location::<impl rustc_mir::interpret::eval_context::InterpCx<M>>::find_closest_untracked_caller_location
             at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/libstd/macros.rs:13
  14: rustc_mir::interpret::intrinsics::<impl rustc_mir::interpret::eval_context::InterpCx<M>>::emulate_intrinsic
             at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/librustc_mir/interpret/intrinsics.rs:102
  15: miri::shims::intrinsics::EvalContextExt::call_intrinsic
             at src/shims/intrinsics.rs:23
  16: <miri::machine::Evaluator as rustc_mir::interpret::machine::Machine>::call_intrinsic
             at src/machine.rs:365

This is a regression introduced by #73246. The likely cause is #73182.

Cc @Aaron1011 @matthewjasper

@LeSeulArtichaut LeSeulArtichaut added A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-miri Area: The miri tool C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. labels Jun 12, 2020
@rustbot rustbot added the I-prioritize Issue: Indicates that prioritization has been requested for this issue. label Jun 12, 2020
@RalfJung RalfJung removed the regression-from-stable-to-nightly Performance or correctness regression from stable to nightly. label Jun 12, 2020
@RalfJung
Copy link
Member Author

@LeSeulArtichaut I removed "regression from stable" as Miri does not exist on stable.

@LeSeulArtichaut
Copy link
Contributor

Sorry, got it.

Dylan-DPC-zz pushed a commit to Dylan-DPC-zz/rust that referenced this issue Jun 12, 2020
@bors bors closed this as completed in 1fb612b Jun 13, 2020
@Dylan-DPC-zz Dylan-DPC-zz removed the I-prioritize Issue: Indicates that prioritization has been requested for this issue. label Jun 14, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-const-eval Area: Constant evaluation, covers all const contexts (static, const fn, ...) A-miri Area: The miri tool C-bug Category: This is a bug. I-ICE Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️ T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants