rust/src/test/run-pass/cleanup-rvalue-temp-during-incomplete-alloc.rs
2016-02-11 12:34:41 +01:00

55 lines
1.5 KiB
Rust

// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
// file at the top-level directory of this distribution and at
// http://rust-lang.org/COPYRIGHT.
//
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
// option. This file may not be copied, modified, or distributed
// except according to those terms.
// Test cleanup of rvalue temporary that occurs while `box` construction
// is in progress. This scenario revealed a rather terrible bug. The
// ingredients are:
//
// 1. Partial cleanup of `box` is in scope,
// 2. cleanup of return value from `get_bar()` is in scope,
// 3. do_it() panics.
//
// This led to a bug because `the top-most frame that was to be
// cleaned (which happens to be the partial cleanup of `box`) required
// multiple basic blocks, which led to us dropping part of the cleanup
// from the top-most frame.
//
// It's unclear how likely such a bug is to recur, but it seems like a
// scenario worth testing.
// ignore-emscripten no threads support
#![allow(unknown_features)]
#![feature(box_syntax)]
use std::thread;
enum Conzabble {
Bickwick(Foo)
}
struct Foo { field: Box<usize> }
fn do_it(x: &[usize]) -> Foo {
panic!()
}
fn get_bar(x: usize) -> Vec<usize> { vec!(x * 2) }
pub fn fails() {
let x = 2;
let mut y: Vec<Box<_>> = Vec::new();
y.push(box Conzabble::Bickwick(do_it(&get_bar(x))));
}
pub fn main() {
thread::spawn(fails).join();
}