|
From: Sabrina L. <sla...@am...> - 2007-03-21 10:38:12
|
> you are using 3.2.3 ? Yes, I confirm: $ valgrind --version valgrind-3.2.3 > you don't have some per-user specific memory limits? (ulimit?) No. Logged as the user, here is the output of the ulimit command: $ ulimit -a cpu time (seconds) unlimited file size (blocks) unlimited data seg size (kbytes) unlimited stack size (kbytes) unlimited core file size (blocks) 16777216 resident set size (kbytes) unlimited processes 73727 file descriptors 32768 locked-in-memory size (kb) unlimited address space (kb) 5242880 file locks unlimited About the prg, I'm going to create and launch it. I'll then let you know. Rgds, Sabtrina Julian Seward <js...@ac...> To val...@li... cc Sabrina Lautier <sla...@am...> bcc Subject Re: [Valgrind-users] Valgrind's memory management: out of memory Julian Seward <js...@ac...> 19/03/2007 16:58 Well, I don't know. Can you check: * you are using 3.2.3 ? * you don't have some per-user specific memory limits? (ulimit?) If you just write a normal program which mallocs 1M blocks in a loop, how much can it allocate before running out of memory? Both when running normally and running on V ? J On Monday 19 March 2007 15:48, Sabrina Lautier wrote: > > valgrind 3.2.X should be able to go up to 32GB on a 64-bit machine. > > Yes, that's what I thought too (the machine is a SuSe SLES9 on an x86_64 > architecture - AMD Opteron). > > > Most likely this machine ran out of swap space. > > No, this is what I checked first of course. > When I monitored the process, there was no swap space in use and only 17% > of the memory was used. > > Rgds, > Sabrina > > > > Julian Seward <js...@ac...> > To > val...@li... > cc > > bcc > > Subject > Re: [Valgrind-users] Valgrind's memory management: out of memory > > > > > > Julian Seward <js...@ac...> > Sent by: val...@li... > 19/03/2007 12:18 > > > When I monitored the process using 'top', I checked that just before > > stopping, the value of the field VIRT was 5055MB and RES around 1.9GB. > > He's binary is 10MB big. > > I guess he faced a valgrind limitation, > > No .. valgrind 3.2.X should be able to go up to 32GB on a 64-bit > machine. Most likely this machine ran out of swap space. > > J > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |