36
Mutex poisoning is not for everyone
(bertptrs.nl)
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Credits
I guess I would have thought panic would trigger other threads to abort as well. Admittedly I haven't really done any multithreading in Rust. I was thinking it was more like
exit(status)in C/C++ that immediately terminated the entire process. Exception unrolling in general I feel is something that should be avoided if you care at all about error conditions.If panics are isolated to one thread, then I guess mutex poisoning is a better default error case than a deadlock where the process never exits. An entirely independent thread might still be unaware the rest of the program has crashed though.
Panics in Rust default to stack unwinding, which I believe is similar to how exceptions work in C++. I don't believe an unhandled exception in C++ kills other threads either? Could be wrong.
Panics can also be configured to instead abort the process immediately, which is the exit(status) way. Obviously with that solution you can never observe a poisoned mutex so you would never need a poisoning mutex in that situation anyway.
An unhandled exception in C++ causes the program to call std::terminate, which calls std::abort by default and brings down the entire program. I don't think there's a way to prevent an unhandled exception from doing that without causing nasal demons, but I could likewise be wrong. According to the standard, regarding the function function called by
std::terminate:A quick check suggests that GCC's
std::terminatecallsstd::abortif your terminate handler does not, but I don't know if that applies to other implementations.EDIT: If anyone else is curious, here is the GCC implementation:
The LLVM version does the same thing.