|
From: Christian P. <tr...@ge...> - 2005-07-22 18:32:31
|
On Wednesday 20 July 2005 16:54, Tom Hughes wrote: > In message <200...@ge...> > > Christian Parpart <tr...@ge...> wrote: > > On Wednesday 20 July 2005 15:39, Nicholas Nethercote wrote: > >> The mmap and munmap calls are very big -- 61680GB and 69390GB > >> respectively. The fact that it happens before the usage message shows > >> this is happening very early. I guess these mmap/munmap calls are from > >> the start-up padding, but then the question is why isn't this causing > >> problems on other AMD64 systems? > > > > I'm having 2GB RAM, and 1GB swap. maybe this matters? > > Besides, why the hell is valgrind m[un]mapping such a huge space (I even > > haven't that much RAM et al) > > It's mapping it to stop anything else being given that part of the > address space - it is how valgrind controls where the OS puts stuff. While using it now some more times, I must unfortunately see, that it becom= es=20 more and more unsuable to me. Those idling times I have to wait until=20 valgrind actually starts and actually exits decrease my productivity :( Is there any way to walk around this? Regards, Christian Parpart. =2D-=20 20:31:10 up 121 days, 9:38, 2 users, load average: 1.34, 2.22, 2.62 |