5de42701a8
The problem was that std::run::Process::new() was unwrap()ing the result of std::io::process::Process::new(), which returns None in the case where the io_error condition is raised to signal failure to start the process. Have std::run::Process::new() similarly return an Option<run::Process> to reflect the fact that a subprocess might have failed to start. Update utility functions run::process_status() and run::process_output() to return Option<ProcessExit> and Option<ProcessOutput>, respectively. Various parts of librustc and librustpkg needed to be updated to reflect these API changes. closes #10754
33 lines
1.2 KiB
Rust
33 lines
1.2 KiB
Rust
// copyright 2013 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.
|
|
|
|
// xfail-fast calling itself doesn't work on check-fast
|
|
|
|
use std::{os, run};
|
|
use std::io::process;
|
|
|
|
fn main() {
|
|
let args = os::args();
|
|
if args.len() >= 2 && args[1] == ~"signal" {
|
|
// Raise a segfault.
|
|
unsafe { *(0 as *mut int) = 0; }
|
|
} else {
|
|
let status = run::process_status(args[0], [~"signal"])
|
|
.expect("failed to exec `signal`");
|
|
// Windows does not have signal, so we get exit status 0xC0000028 (STATUS_BAD_STACK).
|
|
match status {
|
|
process::ExitSignal(_) if cfg!(unix) => {},
|
|
process::ExitStatus(0xC0000028) if cfg!(windows) => {},
|
|
_ => fail!("invalid termination (was not signalled): {:?}", status)
|
|
}
|
|
}
|
|
}
|
|
|