# HG changeset patch
# Parent c821e3a54930c949b8612a3d6bad15059e4a7e43

diff -r c821e3a54930 Doc/library/signal.rst
--- a/Doc/library/signal.rst	Mon Aug 15 14:28:46 2011 +0300
+++ b/Doc/library/signal.rst	Mon Aug 22 15:25:24 2011 +1000
@@ -25,7 +25,11 @@
   calls.
 
 * Because the C signal handler always returns, it makes little sense to catch
-  synchronous errors like :const:`SIGFPE` or :const:`SIGSEGV`.
+  synchronous errors like :const:`SIGFPE` or :const:`SIGSEGV` that are caused
+  by an invalid operation in C code.  Python will return from the signal handler in 
+  to the C code, which is likely to raise the same signal again, causing Python to 
+  apparently hang.  From Python 3.3 onwards, you can use the
+  :mod:`faulthandler` module to report on synchronous errors.
 
 * Python installs a small number of signal handlers by default: :const:`SIGPIPE`
   is ignored (so write errors on pipes and sockets can be reported as ordinary