[issue12423] signal handler doesn't handle SIGABRT from os.abort

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12423] signal handler doesn't handle SIGABRT from os.abort

Howard A. Landman added the comment: I don't think changing the documentation makes this not be a bug. My situation: I have a Python 3.7.3 program that reliably dies (after about 13 hours, having called its measure() method between 118.6M and 118.7M times) with free(): invalid pointer,

[issue12423] signal handler doesn't handle SIGABRT from os.abort

Roundup Robot devnull@devnull added the comment: New changeset 1ac21a715c5d by Victor Stinner in branch '2.7': Issue #12423: Fix os.abort() documentation http://hg.python.org/cpython/rev/1ac21a715c5d New changeset 4e83d8f6d496 by Victor Stinner in branch '3.2': Issue #12423: Fix os.abort()

[issue12423] signal handler doesn't handle SIGABRT from os.abort

STINNER Victor victor.stin...@haypocalc.com added the comment: Here's my proposed patch for the documentation, against the head of the 2.7 branch. Thanks, I applied your pach to 2.7, 3.2 and 3.3 doc. -- resolution: - fixed status: open - closed versions: +Python 3.2, Python 3.3

[issue12423] signal handler doesn't handle SIGABRT from os.abort

Kamil Kisiel ka...@kamilkisiel.net added the comment: Here's my proposed patch for the documentation, against the head of the 2.7 branch. -- keywords: +patch Added file: http://bugs.python.org/file22570/os.rst.patch ___ Python tracker

[issue12423] signal handler doesn't handle SIGABRT from os.abort

Kamil Kisiel ka...@kamilkisiel.net added the comment: The application is interfacing with a C library that uses abort() to signal fatal errors (horrible, I know..). Instead of core dumping I would like to be able to handle these errors at the Python level and do something else. It's starting

[issue12423] signal handler doesn't handle SIGABRT from os.abort

STINNER Victor victor.stin...@haypocalc.com added the comment: Be aware that programs which use signal.signal() to register a handler for SIGABRT will behave differently. I don't understand this sentence. I think that this sentence should be removed, and another should maybe be added. E.g.

[issue12423] signal handler doesn't handle SIGABRT from os.abort

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()

[issue12423] signal handler doesn't handle SIGABRT from os.abort

Changes by Dimitri Tcaciuc dtcac...@gmail.com: -- nosy: +dtcaciuc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12423 ___ ___ Python-bugs-list

[issue12423] signal handler doesn't handle SIGABRT from os.abort

STINNER Victor victor.stin...@haypocalc.com added the comment: Extract of abort manual page: The abort() first unblocks the SIGABRT signal, and then raises that signal for the calling process. This results in the abnormal termination of the process unless the SIGABRT signal is caught and