[SciPy-dev] [INSTALL CVS] segmentation fault

[Pearu Peterson]

On 1 May 2003, Martin Lüthi wrote:

> Hi
> 
> The installation of todays CVS version (2003/05/01) produces a segmentation
> fault on my Linux box. I use the following
> 
> SuSE Linux 8.0, i686
> 
> Python 2.2.2 (#1, Oct 17 2002, 08:48:02) 
> [GCC 2.95.3 20010315 (SuSE)] on linux2
> 
> Numeric 23.0 (Release)
> 
> gcc version 3.2.3
> 
> running python under gdb gives:
> 
> (gdb) run setup.py install
> Starting program: /usr/local/bin/python setup.py install
> [New Thread 1024 (LWP 6290)]
> ### Little Endian detected ####
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 6290)]
> 0x400dbdcb in chunk_free () from /lib/libc.so.6
> 
> (gdb) backtrace 
> #0  0x400dbdcb in chunk_free () from /lib/libc.so.6
> #1  0x400dbc53 in free () from /lib/libc.so.6
> #2  0x40221a53 in array_dealloc (self=0x83020d0) at Src/arrayobject.c:564
> #3  0x4021b4f1 in PyArray_Return (mp=0x83020d0) at Src/arrayobject.c:633

> [Snip]
> 
> Does anybody see the problem? Is the new gcc version to blame?

It's not obvious to me. Mixing different gcc versions is usually not
a problem with pure C codes.
Does Numeric work properly? E.g. check that all tests pass.

Pearu