[SciPy-Dev] segfault from scipy.io.netcdf with scipy-0.14 numpy-0.18

[Robert McGibbon]

fwiw, I did a bisect, and the problem comes at scipy
2dfffc7beeb924d6aa5e6529f25745c5330a7bac.

-Robert


On Thu, May 8, 2014 at 2:26 AM, Robert McGibbon <rmcgibbo at gmail.com> wrote:

> Hey all,
>
> The travis tests for a library I work on just stopped working, and I
> tracked down the bug to the following test case. The file
> "MDTraj/testing/reference/mdcrd.nc" is a netcdf3 file in our repository (
> https://github.com/rmcgibbo/mdtraj/tree/master/MDTraj/testing/reference).
>
> this script:
>
> conda install --yes scipy==0.13 numpy==1.7 --quiet
> python -c 'import scipy.io; print scipy.io.netcdf.netcdf_file("MDTraj/testing/reference/mdcrd.nc").variables["coordinates"][:].sum()'
>
> conda install --yes scipy==0.14 numpy==1.8 --quiet
> python -c 'import scipy.io; print scipy.io.netcdf.netcdf_file("MDTraj/testing/reference/mdcrd.nc").variables["coordinates"][:].sum()'
>
> works on scipy==0.13 numpy==1.7, but segfaults on scipy==0.14 numpy==1.8.
> I got the segfault on both linux and osx.
>
> I tried compiling a new version of numpy from source with debug symbols
> using `python setup.py build_ext -g install`, but couldn't get a useful
> traceback.
>
> $ gdb --core=core
> (gdb) bt
> #0  0x00007fd4f7887b18 in ?? ()
> #1  0x00007fd4f786ecc6 in ?? ()
> #2  0x0000000000000000 in ?? ()
>
>
> Anyone have any advice for tracking this down?
>
> -Robert
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/scipy-dev/attachments/20140508/9b406e79/attachment.html>