rust/tests/ui/sanitize/badfree.rs

// needs-sanitizer-support
// needs-sanitizer-address
//
// compile-flags: -Z sanitizer=address -O
//
// run-fail
// error-pattern: AddressSanitizer: SEGV

use std::ffi::c_void;

extern "C" {
    fn free(ptr: *mut c_void);
}

fn main() {
    unsafe {
        free(1 as *mut c_void);
    }
}
unix: Don't override existing SIGSEGV/BUS handlers Although `stack_overflow::init` runs very early in the process, even before `main`, there may already be signal handlers installed for things like the address sanitizer. In that case, just leave it alone, and don't bother trying to allocate our own signal stacks either. 2020-03-03 23:04:57 +00:00			`// needs-sanitizer-support`
compiletest: Add directives to detect sanitizer support Add needs-sanitizer-{address,leak,memory,thread} directive indicating that test requires target with support for specific sanitizer. This is an addition to the existing needs-sanitizer-support directive indicating that test requires a sanitizer runtime library. 2020-06-05 00:00:00 +00:00			`// needs-sanitizer-address`
unix: Don't override existing SIGSEGV/BUS handlers Although `stack_overflow::init` runs very early in the process, even before `main`, there may already be signal handlers installed for things like the address sanitizer. In that case, just leave it alone, and don't bother trying to allocate our own signal stacks either. 2020-03-03 23:04:57 +00:00			`//`
			`// compile-flags: -Z sanitizer=address -O`
			`//`
			`// run-fail`
			`// error-pattern: AddressSanitizer: SEGV`

			`use std::ffi::c_void;`

			`extern "C" {`
			`fn free(ptr: *mut c_void);`
			`}`

			`fn main() {`
			`unsafe {`
			`free(1 as *mut c_void);`
			`}`
			`}`