New submission from Tim Savannah <tsava...@arinc.com>: I'm getting many segmentation faults (about 1 per half hour) from within the core of python 2.6.2 on 64-bit machines.
(examples from dmesg: pythonLaunch.py[13307]: segfault at 0000000000000058 rip 00002b845cfb3550 rsp 0000000041809930 error 4 pythonLaunch.py[27589]: segfault at 0000000000000058 rip 00002b4112287906 rsp 0000000042dab930 error 4 pythonLaunch.py[14436]: segfault at 0000000000000058 rip 00002ae0a4f68550 rsp 0000000042cd9930 error 4 pythonLaunch.py[10374]: segfault at 0000000000000058 rip 00002af43f966906 rsp 000000004214b930 error 4 pythonLaunch.py[17656]: segfault at 0000000000000058 rip 00002aed0cfe8906 rsp 00000000417f0930 error 4 ) pythonLaunch.py is a symbolic link to python 2.6.2 binary. >From disassembling the python binary, I've found the corrosponding line in source to be ceval.c:2717 if (tstate->frame->f_exc_type != NULL) tstate->frame is null, and an access on f_exc_type causes a segfault (trying to access memory 0x58, see above segfaults). I can't find any clear code path that could cause tstate->frame to go null, any suggestions? This is preventing us from moving from python 2.4 32-bit to python 2.6 64-bit. ---------- components: Interpreter Core messages: 88748 nosy: tsavannah severity: normal status: open title: Core error in Py_EvalFrameEx 2.6.2 type: crash versions: Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6178> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
