rust/tests/ui/panics/panic-set-unset-handler.rs

//@ run-fail
//@ regex-error-pattern: thread 'main' \(\d+\) panicked
//@ error-pattern: foobar
//@ needs-subprocess

use std::panic;

fn main() {
    panic::set_hook(Box::new(|i| {
        eprint!("greetings from the panic handler");
    }));
    panic::take_hook();
    panic!("foobar");
}
Move tests from `test/run-fail` to UI 2020-04-16 15:50:32 +09:00			`//@ run-fail`
Print thread ID in panic message if thread name is unknown `panic!` does not print any identifying information for threads that are unnamed. However, in many cases, the thread ID can be determined. This changes the panic message from something like this: thread '<unnamed>' panicked at src/main.rs:3:5: explicit panic To something like this: thread '<unnamed>' (0xff9bf) panicked at src/main.rs:3:5: explicit panic Stack overflow messages are updated as well. This change applies to both named and unnamed threads. The ID printed is the OS integer thread ID rather than the Rust thread ID, which should also be what debuggers print. 2023-09-11 00:59:31 -04:00			`//@ regex-error-pattern: thread 'main' \(\d+\) panicked`
			`//@ error-pattern: foobar`
tests: use `needs-subprocess` instead of `ignore-{wasm32,emscripten,sgx}` 2025-01-23 16:36:54 +08:00			`//@ needs-subprocess`
Implement custom panic handlers 2015-12-17 23:51:55 -08:00
			`use std::panic;`

			`fn main() {`
std: Clean out old unstable + deprecated APIs These should all have been deprecated for at least one cycle, so this commit cleans them all out. 2016-05-24 14:24:44 -07:00			`panic::set_hook(Box::new(\|i\| {`
Migrate to eprint/eprintln macros where appropriate. 2017-09-25 00:14:56 -04:00			`eprint!("greetings from the panic handler");`
std: Clean out old unstable + deprecated APIs These should all have been deprecated for at least one cycle, so this commit cleans them all out. 2016-05-24 14:24:44 -07:00			`}));`
			`panic::take_hook();`
Implement custom panic handlers 2015-12-17 23:51:55 -08:00			`panic!("foobar");`
			`}`