[INSTALL CVS] segmentation fault
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 #4 0x4022253f in array_add (m1=0x825fca0, m2=0x825fca0) at Src/arrayobject.c:1197 #5 0x080acb1d in binary_op1 (v=0x82d7f78, w=0x82d7fa0, op_slot=0) at Objects/abstract.c:392 #6 0x080af8eb in PyNumber_Add (v=0x82d7f78, w=0x82d7fa0) at Objects/abstract.c:605 #7 0x08076bad in eval_frame (f=0x81ba6b4) at Python/ceval.c:977 #8 0x080799ce in PyEval_EvalCodeEx (co=0x832eea0, globals=0x8338564, locals=0x0, args=0x81ba0e4, argcount=1, kws=0x81ba0e8, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2595 #9 0x0807bb9d in fast_function (func=0x833f09c, pp_stack=0xbfff7c74, n=1, na=1, nk=0) at Python/ceval.c:3170 #10 0x08078a51 in eval_frame (f=0x81b9f94) at Python/ceval.c:2034 #11 0x080799ce in PyEval_EvalCodeEx (co=0x82d7f30, globals=0x8338564, locals=0x8338564, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:2595 #12 0x0807bb38 in PyEval_EvalCode (co=0x82d7f30, globals=0x8338564, locals=0x8338564) at Python/ceval.c:481 [Snip] Does anybody see the problem? Is the new gcc version to blame? Cheers Martin -- Martin L�thi answer@tnoo.net
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
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.
IIRC I had a similar problem, disappearing when using the same gcc version for Python and SciPy... bye, Kasper
Kasper Souren <Kasper.Souren@ircam.fr> writes:
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.
IIRC I had a similar problem, disappearing when using the same gcc version for Python and SciPy...
I will try this, thank you. Best, Martin -- Martin L�thi answer@tnoo.net
participants (3)
-
answer＠tnoo.net -
Kasper Souren -
Pearu Peterson