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

David Cournapeau cournapeau@cslab.kecl.ntt.co...
Thu Nov 20 01:33:47 CST 2008


On Wed, 2008-11-19 at 23:23 -0800, Hoyt Koepke wrote:
> Hello,
> 
> 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

Could you give us the complete build log (e.g. when build from scratch:
remove the build directory and give us the log of python setup.py build
&> build.log) ?

You have tens of failures which are more likely due to a build problem,

David



More information about the Numpy-discussion mailing list