|
From: Nicholas N. <nj...@ca...> - 2004-07-14 10:47:34
|
On Tue, 13 Jul 2004, Howard Chu wrote: >> I get this output, and a message to submit this data.. I have no idea >> what it means, but here it is.. > > It means you ran out of memory. valgrind 2.1.1 appears to be quite a memory > pig compared to previous versions. > >> How do I work around this? > > Installing more RAM in your computer might help. I recall reading on the > -developer list that there's a patch to decrease some of valgrind's demand > for RAM. Hopefully it will be publically released soon. I don't think installing more RAM would help. The issue isn't physical memory, rather address space. 2.1.1 does do not so well here; the current CVS version has some improvements in this respect, and I'm looking at improving things further. The CVS version also no longer asserts when malloc() fails, rather it just returns NULL as standard. If you really need to do big mallocs like this and Memcheck is failing, you could try Addrcheck as it uses less memory. N |