Is it possible to suppress printing of a panic message ("thread panicked at")? I have a parent superviser thread which launches a child thread. The child can sometimes panic, but is safe to just restart. So I don't want to see the default panic message in the stderr and instead I want to provide…

IIRC, you must use the unstable set_hook in std::panic - Rust as you mentioned, and that is the only way.

+1 for ability to customise a panic message. In expectest I'm using panicking::panic_fmt ( here ). It's all good but without "thread panicked at" it would be better. I also think that std::panic::set_hook is overkill for me.

A bit late to this thread, but I'd like to present you with panic_control::spawn_quiet(): [image] Panic-control: Test your panics with peace in mind announcements Recently I tried to test how my code behaves on occurrence of a panic. With only libstd facilities, it turned …

Oh, and this even works on stable because set_hook is now stable? Nice! :heart:

[image] mzabaluev: panics caused on purpose are cumbersome to distinguish from bona fide errors I understood the philosophy that panics in rust are never on purpose and exception handling is not mature enough in rust and not always possible. Result with either item value or an error is the wa…

The crate is basically a test harness helper, used to test how code behaves under a panic. Indeed, it should not be used in any production-destined software (but see below ). That said, in Rust, catching a panic on a thread boundary is a valid failure isolation mechanism. There is also catch_unwind,…

[image] mzabaluev: it should not be used in any production-destined software That's a bit strong statement. Some parts of it, like spawn_quiet and ThreadResultExt, can indeed be used wherever they are needed, such as the use case described at the beginning of this topic.

[image] mzabaluev: There is also catch_unwind, which definitely should not be used for this purpose; its only legitimate use is to prevent unwinding into non-Rust code. I think this is a bit too strong of a statement. catch_unwind can be used to create "less-than-a-thread" isolation boundarie…

Suppress panic message

help

brson June 22, 2016, 4:20am 3

What rustc and libtest do is interesting. They call io::set_panic, an undocumented function, making all of stderr go nowhere.

Topic		Replies	Views
Is there any way to set panic hook reliably in the test? help	1	1074	June 20, 2018
Setting a panic hook in tests help	4	1550	March 9, 2022
Panic-control: Test your panics with peace in mind announcements	0	911	November 29, 2017
Catch panic message help	1	140	November 6, 2025
Re: Test, should_panic: somehow hide stack traces? help	1	560	October 30, 2022

Suppress panic message

Related topics