[Numpy-discussion] glibc memory corruption when running numpy.test()

Hoyt Koepke hoytak@cs.ubc...
Thu Nov 20 01:23:16 CST 2008


Sorry about this bug report.... I know how much us programmers like
these kind of bugs :-/.

In testing the latest svn version of numpy (6083), I get a memory
corruption error:

test_csingle (test_linalg.TestSolve) ... ok
test_double (test_linalg.TestSolve) ... ok
test_empty (test_linalg.TestSolve) ... ok
Check that matrix type is preserved. ... ok
Check that matrix type is preserved. ... ok
test_nonarray (test_linalg.TestSolve) ... ok
test_single (test_linalg.TestSolve) ... ok
Ticket #652 ... *** glibc detected *** python: free(): invalid next
size (fast): 0x0000000002c80ef0 ***

... and it hangs.

I don't get any errors in my installation.  The system is a 64bit
intel xeon server running debian unstable, compiler is gcc-4.3.2

This *doesn't* happen with version 1.2.1.  I do get some other test
failures with that version, which I can post if you all think they are
related, but they don't seem to be at first glance.

I've attached the full log.  If there is anything more you want me to
do with this, I'd be happy to.


+ Hoyt Koepke
+ University of Washington Department of Statistics
+ http://www.stat.washington.edu/~hoytak/
+ hoytak@gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: numpy_test.log.gz
Type: application/x-gzip
Size: 12623 bytes
Desc: not available
Url : http://projects.scipy.org/pipermail/numpy-discussion/attachments/20081119/cdf60d7a/attachment-0001.gz 

More information about the Numpy-discussion mailing list