[SciPy-user] scipy general_function segfault

[Pearu Peterson]

On Thu, 18 Sep 2003, Arnd Baecker wrote:

> and one more:
> 
> I did another reinstall at home. I also managed
> to compile libwadpy.
> 
> However the output is not as helpful as I hoped:
> 
> Alive0c
> WAD: Collecting debugging information...
> WAD: Unable to generate stack trace.
> WAD: Maybe the call stack has been corrupted by buffer overflow.
> zsh: 5332 segmentation fault  ipython
> 
> 
> Independent of this: could the segfault
> be compiler dependent ?
> 
> The cephesmodule.o for cephes.so is compiled
> with gcc 3.3.1:
> 
> gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-linux/3.3.1/specs
> Configured with: ../src/configure -v
> --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
> --mandir=/usr/share/man --infodir=/usr/share/info
> --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
> --with-system-zlib --enable-nls --without-included-gettext
> --enable-__cxa_atexit --enable-clocale=gnu --enable-debug
> --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc i386-linux
> Thread model: posix
> gcc version 3.3.1 20030626 (Debian prerelease)

I have exactly the same setup and the same segfaults occur.
I'll try downgrade Numeric 23.1 now...

Pearu