[Numpy-discussion] Fwd: Package: scipy-0.11.0-0.1.rc2.fc18 Tag: f18-updates-candidate Status: failed Built by: orion

Orion Poplawski orion@cora.nwra....
Wed Feb 13 20:35:11 CST 2013


On 02/13/2013 05:18 PM, Ondřej Čertík wrote:
>>
>> (gdb) up 3
>> #3  0x00007ffff121816c in PyArray_IterNew (obj=<numpy.ndarray at remote
>> 0xe02fd0>)
>>      at numpy/core/src/multiarray/iterators.c:385
>> 385         it = (PyArrayIterObject
>> *)PyArray_malloc(sizeof(PyArrayIterObject));
>> (gdb) print *obj
>> $4 = {ob_refcnt = 5, ob_type = 0x7ffff14c6900 <PyArray_Type>}
>> (gdb) list
>> 380             PyErr_BadInternalCall();
>> 381             return NULL;
>> 382         }
>> 383         ao = (PyArrayObject *)obj;
>> 384
>> 385         it = (PyArrayIterObject
>> *)PyArray_malloc(sizeof(PyArrayIterObject));
>> 386         PyObject_Init((PyObject *)it, &PyArrayIter_Type);
>> 387         /* it = PyObject_New(PyArrayIterObject, &PyArrayIter_Type);*/
>> 388         if (it == NULL) {
>> 389             return NULL;
>
>
> ^^^ This is very useful, thanks! How can it segfault on the line 385 though?
>
> That would suggest that something has gone terribly wrong before and
> this call to malloc simply is the final nail to the coffin.
> Otherwise I thought that malloc can't really segfault like this, can it?
>
> Ondrej
>

Yeah, that's why I didn't think the backtrace would be very useful - 
it's gone off the deep-end long before.  The valgrind reports seem more 
useful.  Need to get the scipy debug stuff installed properly.  I'm 
guessing the interfacing with atlas is not correct.

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  orion@cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com


More information about the NumPy-Discussion mailing list