std: Move running_on_valgrind to rt::util. #1457

[breaking-change]
This commit is contained in:
Brian Anderson 2014-05-20 20:19:39 -07:00
parent 53db981148
commit 1240197a5b
4 changed files with 18 additions and 15 deletions

View File

@ -37,7 +37,7 @@ mod $name {
use io::net::unix::*;
use io::timer::*;
use io::process::*;
use unstable::running_on_valgrind;
use rt::running_on_valgrind;
use str;
fn f() $b

View File

@ -76,6 +76,10 @@
pub use alloc::{heap, libc_heap};
// Used by I/O tests
#[experimental]
pub use self::util::running_on_valgrind;
// FIXME: these probably shouldn't be public...
#[doc(hidden)]
pub mod shouldnt_be_public {

View File

@ -15,11 +15,11 @@
use io;
use iter::Iterator;
use libc;
use libc::uintptr_t;
use option::{Some, None, Option};
use os;
use result::Ok;
use str::{Str, StrSlice};
use unstable::running_on_valgrind;
use slice::ImmutableVector;
// Indicates whether we should perform expensive sanity checks, including rtassert!
@ -162,3 +162,15 @@ fn abort() -> ! {
unsafe { intrinsics::abort() }
}
}
/// Dynamically inquire about whether we're running under V.
/// You should usually not use this unless your test definitely
/// can't run correctly un-altered. Valgrind is there to help
/// you notice weirdness in normal, un-doctored code paths!
pub fn running_on_valgrind() -> bool {
unsafe { rust_running_on_valgrind() != 0 }
}
extern {
fn rust_running_on_valgrind() -> uintptr_t;
}

View File

@ -10,8 +10,6 @@
#![doc(hidden)]
use libc::uintptr_t;
pub use core::finally;
pub mod dynamic_lib;
@ -20,14 +18,3 @@
pub mod sync;
pub mod mutex;
/// Dynamically inquire about whether we're running under V.
/// You should usually not use this unless your test definitely
/// can't run correctly un-altered. Valgrind is there to help
/// you notice weirdness in normal, un-doctored code paths!
pub fn running_on_valgrind() -> bool {
unsafe { rust_running_on_valgrind() != 0 }
}
extern {
fn rust_running_on_valgrind() -> uintptr_t;
}