mirror of
https://github.com/rust-lang/rust.git
synced 2025-09-30 16:26:10 +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.
26 lines
664 B
Rust
26 lines
664 B
Rust
// Checks what happens when formatting the panic message panics.
|
|
|
|
//@ run-crash
|
|
//@ exec-env:RUST_BACKTRACE=0
|
|
//@ check-run-results
|
|
//@ error-pattern: panicked while processing panic
|
|
//@ normalize-stderr: "\n +[0-9]+:[^\n]+" -> ""
|
|
//@ normalize-stderr: "\n +at [^\n]+" -> ""
|
|
//@ normalize-stderr: "(core/src/panicking\.rs):[0-9]+:[0-9]+" -> "$1:$$LINE:$$COL"
|
|
//@ ignore-emscripten "RuntimeError" junk in output
|
|
|
|
use std::fmt::{Display, self};
|
|
|
|
struct MyStruct;
|
|
|
|
impl Display for MyStruct {
|
|
fn fmt(&self, _: &mut fmt::Formatter<'_>) -> fmt::Result {
|
|
todo!()
|
|
}
|
|
}
|
|
|
|
fn main() {
|
|
let instance = MyStruct;
|
|
panic!("this is wrong: {}", instance);
|
|
}
|