New submission from Kamil Kisiel <ka...@kamilkisiel.net>:
It seems that registering a signal handler for SIGABRT doesn't handle the
signal from os.abort().
Example code:
import signal, os
import time
def handler(signum, frame):
print "Signal!"
raise Exception()
signal.signal(signal.SIGABRT, handler)
os.abort()
The result is the process still core dumps instead of raising an exception. If
instead of os.abort I call time.sleep(10) and then send a kill -ABRT from a
shell, the exception is raised as expected.
I tried this with Python 2.6 on Gentoo, 2.7 on FC 14, and 2.6 on OS X 10.6.7
with the same result.
Based on the documentation for os.abort, I would expect this to work:
Generate a SIGABRT signal to the current process. On Unix, the default behavior
is to produce a core dump; on Windows, the process immediately returns an exit
code of 3. Be aware that programs which use signal.signal() to register a
handler for SIGABRT will behave differently.
----------
title: signal handler dpes -> signal handler doesn't handle SIGABRT from
os.abort
versions: +Python 2.6, Python 2.7
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue12423>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
