|
From: Benjamin C. <ben...@si...> - 2006-01-25 14:44:06
|
Hi everyone The solution was simple: throw more hardware at it. Bought an extra gigabyte and now things are as happy as they should be. Thanks for responding Ben Nicholas Nethercote wrote: > On Tue, 24 Jan 2006, Tom Hughes wrote: > >>> The application is a beast taking hundreds of megabytes of dynamic >>> memory. >> >> >> Well that is probably the problem then - error 12 is ENOMEM so most >> likely your program has run out of memory. Don't forget that under >> valgrind it will be using a lot more memory than normal. > > > If you're running Memcheck (the default tool), try running --tool=none, > which will use less memory. > > Nick > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |