mirror of
https://github.com/rust-lang/rust.git
synced 2025-10-02 10:18:25 +00:00
e1d4f2a0c2
And introduce two new directives for ui tests: * `run-crash` * `run-fail-or-crash` Normally a `run-fail` ui test like tests that panic shall not be terminated by a signal like `SIGABRT`. So begin having that as a hard requirement. Some of our current tests do terminate by a signal/crash however. Introduce and use `run-crash` for those tests. Note that Windows crashes are not handled by signals but by certain high bits set on the process exit code. Example exit code for crash on Windows: `0xc000001d`. Because of this, we define "crash" on all platforms as "not exit with success and not exit with a regular failure code in the range 1..=127". Some tests behave differently on different targets: * Targets without unwind support will abort (crash) instead of exit with failure code 101 after panicking. As a special case, allow crashes for `run-fail` tests for such targets. * Different sanitizer implementations handle detected memory problems differently. Some abort (crash) the process while others exit with failure code 1. Introduce and use `run-fail-or-crash` for such tests.
16 lines
456 B
Rust
16 lines
456 B
Rust
//@ run-crash
|
|
//@ compile-flags: -Cdebug-assertions=yes
|
|
//@ error-pattern: unsafe precondition(s) violated: Vec::from_parts_in requires that length <= capacity
|
|
#![feature(allocator_api)]
|
|
|
|
use std::ptr::NonNull;
|
|
|
|
fn main() {
|
|
let ptr: NonNull<i32> = std::ptr::NonNull::dangling();
|
|
// Test Vec::from_parts_in with length > capacity
|
|
unsafe {
|
|
let alloc = std::alloc::Global;
|
|
let _vec = Vec::from_parts_in(ptr, 10, 5, alloc);
|
|
}
|
|
}
|