[Numpy-discussion] advanced indexing bug with huge arrays?

[Charles R Harris]

On Tue, Jan 24, 2012 at 3:30 PM, David Warde-Farley <
wardefar at iro.umontreal.ca> wrote:

> On Tue, Jan 24, 2012 at 01:02:44PM -0500, David Warde-Farley wrote:
> > On Tue, Jan 24, 2012 at 06:37:12PM +0100, Robin wrote:
> >
> > > Yes - I get exactly the same numbers in 64 bit windows with 1.6.1.
> >
> > Alright, so that rules out platform specific effects.
> >
> > I'll try and hunt the bug down when I have some time, if someone more
> > familiar with the indexing code doesn't beat me to it.
>
> I've figured it out. In numpy/core/src/multiarray/mapping.c, PyArray_GetMap
> is using an int for a counter variable where it should be using an
> npy_intp.
>
> I've filed a pull request at https://github.com/numpy/numpy/pull/188 with
> a
> regression test.
>
>
I think this bug, or one like it, was reported a couple of years ago. But I
don't recall if there was ever a ticket opened.

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