[Numpy-discussion] segmentation fault
Wed May 28 10:07:16 CDT 2008
On Wednesday 28 May 2008 10:51:20 am Alan McIntyre wrote:
> On Wed, May 28, 2008 at 10:30 AM, Keith Goodman <email@example.com>
> > Does anyone else get this seg fault?
> >>> def fn():
> > x = np.random.rand(5,2)
> > x.cumsum(None, out=x)
> > return x
> > ....:
> >>> fn()
> > *** glibc detected *** /usr/bin/python: double free or corruption
> > (out): 0x08212dc8 ***
> > I'm running 1.0.4 from Debian Lenny with python 2.5.2 compiled with
> > gcc 4.2.3-3, if that matters.
> Yep I get one here too, using numpy and Python 2.5 from svn trunk.
> It doesn't always happen on the first invocation of the function.
Ah. That appears to be correct. My last posting said that I didn't see
this. But after running it a few times I get a segfault.
Scott M. Ransom Address: NRAO
Phone: (434) 296-0320 520 Edgemont Rd.
email: firstname.lastname@example.org Charlottesville, VA 22903 USA
GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989
More information about the Numpy-discussion