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

Ondřej Čertík ondrej.certik@gmail....
Fri Sep 21 12:41:24 CDT 2012


Hi Orion,

On Thu, Sep 20, 2012 at 2:56 PM, Orion Poplawski <orion@cora.nwra.com> wrote:
> This is a plea for some help.  We've been having trouble getting scipy to
> pass all of the tests in the Fedora 18 build with python 3.3 (although it
> seems to build okay in Fedora 19).  Below are the logs of the build.  There
> appears to be some kind of memory corruption that manifests itself a little
> differently on 32-bit vs. 64-bit.  I really have no idea myself how to
> pursue debugging this, though I'm happy to provide any more needed
> information.

Thanks for testing the latest beta2 release.

> Task 4509077 on buildvm-35.phx2.fedoraproject.org
> Task Type: buildArch (scipy-0.11.0-0.1.rc2.fc18.src.rpm, i686)
> logs:
>   http://koji.fedoraproject.org/koji/getfile?taskID=4509077&name=build.log

This link has the following stacktrace:

/lib/libpython3.3m.so.1.0(PyMem_Free+0x1c)[0xbf044c]
/usr/lib/python3.3/site-packages/numpy/core/multiarray.cpython-33m.so(+0x4d52b)[0x42252b]
/usr/lib/python3.3/site-packages/numpy/core/multiarray.cpython-33m.so(+0xcb7c5)[0x4a07c5]
/usr/lib/python3.3/site-packages/numpy/core/multiarray.cpython-33m.so(+0xcbc5e)[0x4a0c5e]

Which indeed looks like in NumPy. Would you be able to obtain full stacktrace?

There has certainly been segfaults in Python 3.3 with NumPy, but we've
fixed all that we could reproduce. That doesn't mean there couldn't be
more. If you could nail it down a little bit more, that would be
great. I'll help once I can reproduce it somehow.

Ondrej


More information about the NumPy-Discussion mailing list