[issue1215] Python hang when catching a segfault

Adam Olsen report at bugs.python.org
Sun Jan 13 00:20:24 CET 2008


Adam Olsen added the comment:

The warning in the documentation should be strengthened.  Python simply
does not and cannot support synchronously-generated signals.

It is possible to send a normally synchronous signal asynchronously,
such as the os.kill() Ralf mentioned, so it's theoretically possible to
use custom handlers for them.  However, I can't think of any real use
cases, and having such a handler would be asking for trouble if a real
synchronously-generated signal was produced.  I guess that's an argument
for not allowing custom handlers. ;)

Suggested documentation:
"Because of the precarious nature of how synchronously-generated signals
must be handled, the signal module does not allow installing handlers
for them.  This includes SIGSEGV, SIGFPE, SIGBUS, SIGILL, SIGABRT..."

I haven't been able to find a canonical list if synchronously-generated
signals.  Furthermore, I've seen conflicting claims about SIGABRT.

----------
nosy: +Rhamphoryncus

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1215>
__________________________________


More information about the Python-bugs-list mailing list