[Numpy-discussion] Testsuite fails with Python 2.7.3rc1 and 3.2.3rc1 (Debian)
Charles R Harris
Sat Apr 7 21:01:22 CDT 2012
On Sat, Apr 7, 2012 at 7:04 PM, Charles R Harris
> On Sat, Apr 7, 2012 at 6:41 PM, Charles R Harris <
> firstname.lastname@example.org> wrote:
>> On Sat, Apr 7, 2012 at 5:32 PM, Sandro Tosi <email@example.com> wrote:
>>> On Sun, Apr 1, 2012 at 12:25, Ralf Gommers <firstname.lastname@example.org>
>>> > OK, that makes sense. So there are six test runs; for normal and debug
>>> > builds of 2.6.7, 2.7.3rc1 and 3.2.3rc2. Only the debug builds of the
>>> > have a problem, debug build of 2.6.7 is fine.
>>> > So I'd think that most likely there is a problem with how the debug
>>> > of the RCs were built.
>>> it sounds possible: is there a way to isolate the failing test, so
>>> that I can provide a minimal test code for further investigation to
>>> python maintainer?
>> Possibly related to ticket #1578<http://projects.scipy.org/numpy/ticket/1578>.
> I can reproduce at least one crash with python2.7 debug at arrayobject.c
> Program received signal SIGSEGV, Segmentation fault.
> 0x00000036a5882b94 in free () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00000036a5882b94 in free () from /lib64/libc.so.6
> #1 0x00007ffff12ce399 in array_dealloc (self=0x1bc50d8)
> at numpy/core/src/multiarray/arrayobject.c:408
> #2 0x00007ffff12b58dd in PyArray_Return (mp=0x1bc50d8)
> at numpy/core/src/multiarray/scalarapi.c:830
> #3 PyArray_Return (mp=0x1bc50d8) at
> #4 0x00007ffff12b5d68 in array_any (array=0x1b69de8, args=<optimized
> kwds=<optimized out>) at numpy/core/src/multiarray/methods.c
> I don't know if it is the same.
This one occurs in test_api.test_copyto_fromscalar.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion