[Numpy-discussion] numpy core dump on linux

[Charles R Harris]

On Wed, Sep 2, 2009 at 5:19 PM, Citi, Luca <lciti at essex.ac.uk> wrote:

> I experience the same problem.
> A few more additional test cases:
>
> In [1]: import numpy
>
> In [2]: numpy.lexsort([numpy.arange(5)[::-1].copy(), numpy.arange(5)])
> Out[2]: array([0, 1, 2, 3, 4])
>
> In [3]: numpy.lexsort([numpy.arange(5)[::-1].copy(), numpy.arange(5.)])
> Out[3]: array([0, 1, 2, 3, 4])
>
> In [4]: numpy.lexsort([numpy.arange(5), numpy.arange(5)])
> Out[4]: array([0, 1, 2, 3, 4])
>
> In [5]: numpy.lexsort([numpy.arange(5), numpy.arange(5.)])
> Out[5]: array([0, 1, 2, 3, 4])
>
> In [6]: numpy.lexsort([numpy.arange(5)[::-1], numpy.arange(5)])
> Out[6]: array([0, 1, 2, 3, 4])
>
> In [7]: numpy.lexsort([numpy.arange(5)[::-1], numpy.arange(5.)])
> *** glibc detected *** /usr/bin/python: free(): invalid next size (fast):
> 0x09be6eb8 ***
>
> It looks like the problem is when the first array is reversed and the
> second is float.
>
> I am not familiar with gdb. If I run "gdb python", run it, and give the
> commands above,
> it hangs at the glibc line without returning to gdb unless I hit CTRL-C. In
> this case,
> I guess, the backtrace I get is related to the CTRL-C rather than the
> error.
> Any hint in how to obtain useful information from gdb?
>
>
The actual bug is probably not where the crash occurs. I think there is
enough info to track it down for anyone who wants to crawl through the
relevant code.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20090902/c711c9d7/attachment.html>