[Numpy-discussion] segfault in numpy.float64(z) for complex z

Stefan van der Walt stefan at sun.ac.za
Mon Jan 8 17:50:24 CST 2007


On Tue, Jan 09, 2007 at 10:38:06AM +1100, Tim Leslie wrote:
> On 1/9/07, Stefan van der Walt <stefan at sun.ac.za> wrote:
> > On Mon, Jan 08, 2007 at 08:11:03AM -0700, Travis Oliphant wrote:
> > > Tim Leslie wrote:
> > >
> > > >Hi All,
> > > >
> > > >While debugging a scipy crash I came across the problem outlined in
> > > >
> > > >http://projects.scipy.org/scipy/numpy/ticket/412
> > > >
> > > >Could someone shed some light on why this is happening, I got a bit
> > > >lost in the numpy internals when I tried to track it down.
> > > >
> > > >
> > > >
> > >
> > > Recent changes to arrtype_new no doubt.   If somebody with a non-SVN
> > > version of numpy could verify that would be great.
> >
> > How recent?  This was broken in r2679 already.
> 
> It looks like it's due to changes in r3493
> 
> http://projects.scipy.org/scipy/numpy/changeset/3493
> 
> The line at which it barfs is:
> 
>         if (robj->ob_type == type) return robj;
> 
> which is a new piece of code from this changeset.

You're right -- it wasn't broken in r2679 -- I had a newer version of
multiarray lying around.  You may proceed to kick me in the head now.

Cheers
Stéfan


More information about the Numpy-discussion mailing list