[Numpy-discussion] NumPy segfault when running tests (2.7, 1.4.1)

David Warde-Farley dwf@cs.toronto....
Tue Aug 3 14:52:55 CDT 2010


This was using the Intel MKL/icc to compile NumPy and also icc to compile Python on a shared cluster, but I don't think that's relevant given where the segmentation fault occurs...

gpc-f104n084-$ gdb python
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) 
(gdb) run    
Starting program: /home/dwf/pkg/bin/python 
[Thread debugging using libthread_db enabled]
Python 2.7 (r27:82500, Aug  3 2010, 15:33:51) 
[GCC Intel(R) C++ gcc 4.1 mode] on linux2
Type "help", "copyright", "credits" or "license" for more information.
[New Thread 0x2b76149111a0 (LWP 23034)]
>>> import numpy
numpy>>> numpy.test()
Running unit tests for numpy
NumPy version 1.4.1
NumPy is installed in /home/dwf/pkg/lib/python2.7/site-packages/numpy
Python version 2.7 (r27:82500, Aug  3 2010, 15:33:51) [GCC Intel(R) C++ gcc 4.1 mode]
nose version 0.11.4
...................................................................................................................................
Program received signal SIGSEGV, Segmentation fault.
0x0000000000500916 in PyErr_WarnEx (category=0x11eb6c54, 
    text=0x5f90c0 "PyOS_ascii_strtod and PyOS_ascii_atof are deprecated.  Use PyOS_string_to_double instead.", stack_level=0) at Python/_warnings.c:719
719	    res = do_warn(message, category, stack_level);
(gdb) 



More information about the NumPy-Discussion mailing list