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 to sound like that might be impossible.
You explanation of the abort() behaviour makes sense to me. However, if that's the case then this portion of the docs appears to be incorrect: "Be aware that programs which use signal.signal() to register a handler for SIGABRT will behave differently." Maybe my interpretation is wrong, but I would read "behave differently" as "call the signal handler instead" in this case. ---------- _______________________________________ 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
