-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Compiler panic - assertion failed: !self.has_escaping_regions() #26638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Does this reproduce on 1.2.0 (or nightly)? If not, could you provide us the source? |
Here is the trace from 1.3.0 nightly $ RUST_BACKTRACE=1 rustc src/main.rs stack backtrace: |
Uploaded the code that produces the problem here |
Reduces to fn parse_type(iter: Iterator<Item=&str>) -> (&str, usize) { panic!() }
fn main() {} |
I think I've tracked this down to a bug in ty::accumulate_lifetimes_in_type: it ignores the trait's Binder, and therefore returns a region with the wrong De Bruijn index. @nikomatsakis , you were the last one to touch this, I think? |
Compiler panic. Found an ealier issue in the same file that had been closed because the problem had gone away in later compiles. This is the stable 1.1 though.
Version info
rustc 1.1.0 (35ceea3 2015-06-19)
binary: rustc
commit-hash: 35ceea3
commit-date: 2015-06-19
host: x86_64-pc-windows-gnu
release: 1.1.0
RUST_BACKTRACE=1 rustc --verbose src/main.rs
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: run with
RUST_BACKTRACE=1
for a backtracethread 'rustc' panicked at 'assertion failed: !self.has_escaping_regions()', C:/bot/slave/stable-dist-rustc-win-gnu-64/build/src/librustc\middle\ty.rs:2123
stack backtrace:
1: 0x6f138a02 - sys::backtrace::write::hb142593d131303b10fs
2: 0x6f141e76 - rt::unwind::register::h2f2891f465b0e536sNv
3: 0x6f1053c0 - rt::unwind::begin_unwind_inner::he5d025d7f655ecaaCKv
4: 0x6d08989e - middle::astencode::rbml..Doc<'a>.doc_decoder_helpers::opt_child::hd6aba4d7b00f0fc9UKb
5: 0x6d1c0773 - middle::traits::fulfill::FulfillmentContext<'tcx>::register_builtin_bound::h1fba927ecfad50a9DEO
6: 0x6a93c978 - check::FnCtxt<'a, 'tcx>.mc..Typer<'tcx>::is_method_call::hb206e83d494db5a0Akn
7: 0x6a948ac8 - check::FnCtxt<'a, 'tcx>.AstConv<'tcx>::projected_ty::he778b71de0699925wAo
8: 0x6a95effc - check::CheckItemBodiesVisitor<'a, 'tcx>.Visitor<'tcx>::visit_item::h49b5aaa3aec9c80dWrn
9: 0x6a95d1df - check::CheckItemBodiesVisitor<'a, 'tcx>.Visitor<'tcx>::visit_item::h49b5aaa3aec9c80dWrn
10: 0x6aa187ab - check_crate::hf98f1f239eb0b1afsJC
11: 0x6aa11f75 - check_crate::hf98f1f239eb0b1afsJC
12: 0x6701f3dd - driver::phase_3_run_analysis_passes::h5d9dbc988e0fcdbatGa
13: 0x67002b40 - driver::compile_input::h66ba80b489f2ef28Qba
14: 0x670b5913 - run_compiler::hf1308c7d75cfa1a775b
15: 0x670b349f - run::h99d8d2bce2d42189N5b
16: 0x670b2a59 - run::h99d8d2bce2d42189N5b
17: 0x6f17b5bc - rust_try
18: 0x6f17b599 - rust_try
19: 0x670b2cd5 - run::h99d8d2bce2d42189N5b
20: 0x6f140134 - sys::process::Command::cwd::hecbd2393e1ca7c52luu
21: 0x776659cd - BaseThreadInitThunk
The text was updated successfully, but these errors were encountered: