[issue14173] PyOS_FiniInterupts leaves signal.getsignal segfaulty

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> 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.
0x000000000052b87b in signal_getsignal (self=<module at remote 0x7ffff7f43a38>, args=(1,))
    at ./Modules/signalmodule.c:372
372	    Py_INCREF(old_handler);
Missing debug package(s), you should install: glibc-debug-2.12.1-11.3.mga1.x86_64
(gdb) bt
#0  0x000000000052b87b in signal_getsignal (self=<module at remote 0x7ffff7f43a38>, args=(1,))
    at ./Modules/signalmodule.c:372
#1  0x00000000005f520b in PyCFunction_Call (func=
    <built-in method getsignal of module object at remote 0x7ffff7f43a38>, arg=(1,), kw=0x0)
    at Objects/methodobject.c:81

----------
nosy: +haypo, pitrou
versions: +Python 3.3 -Python 2.6, Python 3.1
Added file: http://bugs.python.org/file24706/sig.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14173>
_______________________________________