[issue14173] PyOS_FiniInterupts leaves signal.getsignal segfaulty

2013-05-04 Thread Antoine Pitrou
Antoine Pitrou added the comment: This should be fixed now. Thank you for diagnosing this bug! -- resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 3.4 -Python 3.2 ___ Python tracker

[issue14173] PyOS_FiniInterupts leaves signal.getsignal segfaulty

2013-05-04 Thread Roundup Robot
Roundup Robot added the comment: New changeset 0201d8fa8bd0 by Antoine Pitrou in branch '2.7': Issue #14173: Avoid crashing when reading a signal handler during interpreter shutdown. http://hg.python.org/cpython/rev/0201d8fa8bd0 New changeset 0dfd5c7d953d by Antoine Pitrou in branch '3.3': Issu

[issue14173] PyOS_FiniInterupts leaves signal.getsignal segfaulty

2012-03-02 Thread Antoine Pitrou
Antoine Pitrou added the comment: I needed to modify the script to make it crash under 3.2/3.3. Attaching modified version. Here is the relevant part of the gdb traceback: Program received signal SIGSEGV, Segmentation fault. 0x0052b87b in signal_getsignal (self=, args=(1,)) at ./

[issue14173] PyOS_FiniInterupts leaves signal.getsignal segfaulty

2012-03-02 Thread Ferringb
New submission from Ferringb : During Py_Finalize (pythonrun.c), it does the following: 1) suppress signal handling PyOs_FiniInterupts 2) clear caches 3) force gc collection; first for objects, then via wiping modules. The problem is that for unix OSs, Modules/signal.c's PyOs_FiniInterrupts leav