task 'rustc' failed at 'index out of bounds: the len is 0 but the index is 0'

[glennw]

The following code snippet reproduces an ICE:

use std::io::File;

pub struct Block<'a> {
    file: &'a mut File,
}

impl<'a> Drop for Block<'a> {
    fn drop(&mut self) {
    }
}

fn main() {
}

This is from a nightly build on Ubuntu 14.04.

rustc 0.11.0-pre-nightly (4fdc27e 2014-06-10 23:37:06 -0700)
host: x86_64-unknown-linux-gnu

The backtrace is:

task 'rustc' failed at 'index out of bounds: the len is 0 but the index is 0', /home/rustbuild/src/rust-buildbot/slave/nightly-linux/build/src/librustc/lib.rs:1

stack backtrace:
   1:     0x7fc8cdad8c10 - rt::backtrace::imp::write::h0f38c539dbcda993jft::v0.11.0.pre
   2:     0x7fc8cdae0340 - failure::on_fail::h79f8b01a980e0c17zAt::v0.11.0.pre
   3:     0x7fc8ce2efad0 - unwind::begin_unwind_inner::hf48ddea4e5ee9592x2c::v0.11.0.pre
   4:     0x7fc8ce2ef560 - unwind::begin_unwind_fmt::h2846140e9d8152bbZZc::v0.11.0.pre
   5:     0x7fc8ce2ef520 - rust_begin_unwind
   6:     0x7fc8ce33e400 - failure::begin_unwind::hf4ad5bd15101ffa5XWv::v0.11.0.pre
   7:     0x7fc8ce342390 - failure::fail_bounds_check::h6acd523f8d39dc637Uv::v0.11.0.pre
   8:     0x7fc8ceb186f0 - middle::ty_fold::super_fold_sty::h3730223753731460619::v0.11.0.pre
   9:     0x7fc8ce946340 - middle::subst::SubstFolder<'a>.TypeFolder::fold_ty::hcb1c14bdd9058af1bbT::v0.11.0.pre
  10:     0x7fc8ce946250 - middle::subst::T.Subst::subst_spanned::h13092793717765111244::v0.11.0.pre
  11:     0x7fc8ceaaeae0 - middle::ty::lookup_field_type::h991df4aec0cce5d3mxR::v0.11.0.pre
  12:     0x7fc8ce9849b0 - middle::ty::struct_fields::h84685340d7be1defGFR::v0.11.0.pre
  13:     0x7fc8ceadc460 - middle::ty::type_contents::tc_ty::hce1499fcea4030feCNO::v0.11.0.pre
  14:     0x7fc8cea842d0 - middle::ty::type_contents::hcaff03acebb12d14yMO::v0.11.0.pre
  15:     0x7fc8cee693b0 - middle::kind::check_item::ha3af69f9a195adefWlU::v0.11.0.pre
  16:     0x7fc8cee6c240 - middle::kind::check_crate::hea7b3717fee2a23bbcU::v0.11.0.pre
  17:     0x7fc8cf2134f0 - driver::driver::phase_3_run_analysis_passes::h7b807a494581c5a43io::v0.11.0.pre
  18:     0x7fc8cf20baa0 - driver::driver::compile_input::ha1ba02b405e442f1u7n::v0.11.0.pre
  19:     0x7fc8cf2d60d0 - driver::run_compiler::h8ba4b1467c3ca0c8aNq::v0.11.0.pre
  20:     0x7fc8cf2d5ff0 - driver::main_args::closure.95425
  21:     0x7fc8cf2f0880 - driver::monitor::closure.96487
  22:     0x7fc8cf2ebb20 - task::TaskBuilder::try::closure.96250
  23:     0x7fc8d13201c0 - task::spawn_opts::closure.7123
  24:     0x7fc8ce2ed080 - task::Task::run::closure.5036
  25:     0x7fc8ce358b50 - rust_try
  26:     0x7fc8ce2ef0c0 - unwind::try::h2aae115cf1cb1928TQc::v0.11.0.pre
  27:     0x7fc8ce2ecf00 - task::Task::run::h1273187bf2200f61qxc::v0.11.0.pre
  28:     0x7fc8d131ff60 - task::spawn_opts::closure.7096
  29:     0x7fc8cdad8060 - rt::thread::thread_start::h9379ba9e30dffcfecAs::v0.11.0.pre
  30:     0x7fc8cd80f0c0 - start_thread
  31:     0x7fc8cdfc02d9 - __clone
  32:                0x0 - <unknown>

[jdm]

Looks like a dup of #13853.

[jdm]

In fact it's an exact dup of my testcase in that issue.