On Mon, 01 Aug 2011 16:48:35 +0200, Sebastian Reitenbach wrote:
On Monday, August 1, 2011 12:49 CEST, David Coppa <dco...@gmail.com>
wrote:
On Mon, Aug 1, 2011 at 12:40 PM, Sebastian Reitenbach
<sebas...@l00-bugdead-prods.de> wrote:
>
> On Friday, July 29, 2011 16:25 CEST, "Sebastian Reitenbach"
<sebas...@l00-bugdead-prods.de> wrote:
>
>> trying to compile python on a sparc with 5.0 snapshot ends up
with a segfault of python itself:
>
> out of curiosity I tried python-2.5, and the same happens here
too:
>
> Compiling
/home/ports/pobj/Python-2.5.4/fake-sparc/usr/local/lib/python2.5/test/test_bufio.py
...
> Compiling
/home/ports/pobj/Python-2.5.4/fake-sparc/usr/local/lib/python2.5/test/test_builtin.py
...
> Segmentation fault (core dumped)
http://bugs.python.org/issue7424
http://gnats.netbsd.org/42627
Hi,
after few tests with Sebastian and Python's team, result is:
"The problem with such issues is that:
- they are not reproduceable by someone of the core team
- they only seem to occur in non-debug mode
- they are probably tied to a specific compiler variant, either because
of a compiler bug, or some aggressive optimization combined with some
misled assumption in Python's code
To narrow it down, you could:
- try with other compiler versions
- try with other Python versions from python.org (for example the
recent 3.2.1)"
Someone who hack on sparc could help ?
Thanks a lot,
Remi.
