[Numpy-discussion] NumPy SVN broken

Stéfan van der Walt stefan@sun.ac...
Tue Oct 6 11:46:20 CDT 2009

2009/10/6 Charles R Harris <charlesr.harris@gmail.com>:
> 2009/10/6 Stéfan van der Walt <stefan@sun.ac.za>
>> Hi all,
>> The current SVN HEAD of NumPy is broken and should not be used.
>> Extensions compiled against this version may (will) segfault.
> Can you be more specific? I haven't had any problems running current svn
> with scipy.

Both David and I had segfaults when running scipy compiled off
the latest numpy.  An example from Kiva:

Program received signal SIGSEGV, Segmentation fault.
PyArray_INCREF (mp=0x42)
    at build/scons/numpy/core/src/multiarray/refcount.c:103
103	    if (!PyDataType_REFCHK(mp->descr)) {
(gdb) bt
#0  PyArray_INCREF (mp=0x42)
    at build/scons/numpy/core/src/multiarray/refcount.c:103
#1  0x00985f67 in agg::pixel_map_as_unowned_array (pix_map=...)
    at build/src.linux-i686-2.6/enthought/kiva/agg/src/x11/plat_support_wrap.cpp:2909
#2  0x0098795f in _wrap_pixel_map_as_unowned_array (args=0xb7ed032c)
    at build/src.linux-i686-2.6/enthought/kiva/agg/src/x11/plat_support_wrap.cpp:3341

Via bisection, the source of the problem has been localised to the
merge of the datetime branch.


More information about the NumPy-Discussion mailing list