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
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 0058 rip
2b845cfb3550 rsp 41809930 error 4
Tim Savannah tsava...@arinc.com 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
Tim Savannah tsava...@arinc.com 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
Tim Savannah tsava...@arinc.com 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
Tim Savannah tsava...@arinc.com added the comment:
to update, no additional output was seen from pydebug.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6178
New submission from Tim Savannah <kata...@gmail.com>:
Hello!
This is my first time submitting to Python bug tracker, so please bear with me
if I miss/mess something.
So a little bit of relevant background, I'm an avid python developer with many
open-source projects.
One of the proj
