From a12f5119101060909de1938d7d4a96854cc02780 Mon Sep 17 00:00:00 2001 From: Sebastian Dröge Date: Thu, 2 Nov 2017 18:30:02 +0200 Subject: Mention that panics can't possibly be caught when compiling with panic=abort --- src/libstd/thread/mod.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/libstd/thread') diff --git a/src/libstd/thread/mod.rs b/src/libstd/thread/mod.rs index da5965d801c..97220ad993b 100644 --- a/src/libstd/thread/mod.rs +++ b/src/libstd/thread/mod.rs @@ -26,7 +26,7 @@ //! Fatal logic errors in Rust cause *thread panic*, during which //! a thread will unwind the stack, running destructors and freeing //! owned resources. While not meant as a 'try/catch' mechanism, panics -//! in Rust can nonetheless be caught with +//! in Rust can nonetheless be caught (unless compiling with `panic=abort`) with //! [`catch_unwind`](../../std/panic/fn.catch_unwind.html) and recovered //! from, or alternatively be resumed with //! [`resume_unwind`](../../std/panic/fn.resume_unwind.html). If the panic -- cgit 1.4.1-3-g733a5