|
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. |