|
From: Thomas W. <tw...@gl...> - 2006-05-17 17:06:35
|
I'm using valgrind-3.0.1.SVN as shipped with SuSE Linux 10, on an AMD64 box. My code maps several hundred very large images into memory - a total of about fifteen gigabytes. Running without valgrind, it works without trouble; with valgrind, the seventh and subsequent mmaps fail. These are read-only mmaps, so the question of definedness probably oughtn't to apply; is there any way to tell valgrind not to care about the huge mappings? Thomas Womack, Global Phasing Ltd. |
|
From: Julian S. <js...@ac...> - 2006-05-17 17:17:43
|
3.0.X on amd64 simply inherited the x86 port's address space management, which means you can't use more than 4G ever. Try 3.1.1 or (better) the current svn trunk. 3.1.0 and later support up to 32G memory on amd64, which gives you about 14G usable for 3.1.1. The trunk has a more compact representation of definedness bits and so you should be good for up to 22+ G using that. J On Wednesday 17 May 2006 18:06, Thomas Womack wrote: > I'm using valgrind-3.0.1.SVN as shipped with SuSE Linux 10, on an AMD64 > box. > > My code maps several hundred very large images into memory - a total of > about fifteen gigabytes. > > Running without valgrind, it works without trouble; with valgrind, the > seventh and subsequent mmaps fail. > > These are read-only mmaps, so the question of definedness probably > oughtn't to apply; is there any way to tell valgrind not to care about > the huge mappings? > > > Thomas Womack, Global Phasing Ltd. > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Nicholas N. <nj...@cs...> - 2006-05-17 18:59:08
|
On Wed, 17 May 2006, Julian Seward wrote: > Try 3.1.1 or (better) the current svn trunk. 3.1.0 and later > support up to 32G memory on amd64, which gives you about 14G > usable for 3.1.1. The trunk has a more compact representation > of definedness bits and so you should be good for up to 22+ G > using that. Or even more; if the maps are large and read-only they should be represented very compactly (only one pointer per 64KB). Nick |