[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: > As an update (since someone else has this problem) this issue stopped > once we converted from centos to archlinux (www.archlinux.org). May be > an underlying issue with something in the centos environment. We used > the same modules same configuration basic

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: As an update (since someone else has this problem) this issue stopped once we converted from centos to archlinux (www.archlinux.org). May be an underlying issue with something in the centos environment. We used the same modules same configuration basically same

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Chris Kaynor added the comment: Was any resolution found for this? I am debugging some intermittent crashes now which have the same visible callstack as Tim reported. tstate->frame is NULL on line 2717 of ceval.c I am using an in-house compiled Python 2.6.4, compiled with Visual Studio 2008,

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: to update, no additional output was seen from pydebug. -- ___ Python tracker ___ ___ Python-bugs-list

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: recompiled with pydebug enabled, and recompiled all site-packages. Still getting exceptions, however they are occuring within the python binary now and not libpython2.6.1 . pythonLaunch.py[25914]: segfault at 0068 rip 004c7694 rsp 4181

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: > And no, there is still segfaults without optimizations, I've tried at > -O2 -O and -O0 ( -O0 being no optimization). Then you can try rebuilding Python after "./configure --with-pydebug". It will add some runtime checks, perhaps it will find the cause of the

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Changes by Marshall Roach : -- nosy: +mroach ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: All site-packages were compiled against python 2.6.1, and python was upgraded later to 2.6.2 (but upon running a make install with python 2.6.2, it seemed to recompile site-packages on a byte-code level). And no, there is still segfaults without optimizations, I'

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: If the third-party packages include some C extensions, have they been recompiled with the new Python build? Also, does the segfault disappear if you disable optimizations? Have you tried with another compiler version? (I'm asking all this because to my knowled

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Tim Savannah added the comment: Yes I compiled python myself, using ./configure --prefix=/usr/local/python2.6/ --with-pth --enable-shared It is a 64-bit compile. I've done this with both standard config and a config that I modded which produces optimizations options as -ggdb3 -O0. Both contain

[issue6178] Core error in Py_EvalFrameEx 2.6.2

Antoine Pitrou added the comment: Have you compiled Python yourself? Are you using any third-party C extensions? -- nosy: +pitrou ___ Python tracker ___ _

[issue6178] Core error in Py_EvalFrameEx 2.6.2

New submission from Tim Savannah : 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 0058 rip 2b845cfb3550 rsp 41809930 error 4 pythonLaunch.py[27