|
From: Edward M. <edw...@ce...> - 2005-02-06 09:52:15
|
Hi all, We've been having problems getting valgrind 2.2.0 working with our project. Older versions (e.g. <2.0.0) seemed to work okay. One of our IT folk says that since (according to the valgrind manual) MemCheck takes ~12 times more memory than usually needed, and our code takes 1Gb normally, valgrind will never work. Apparently the maximum addressable space on a 32-bit processor is 4Gb, so "unless you do something really smart with your swap space, you can never run valgrind" Is this correct? Has something drastic changed since the 1.x.x days? Do all the valgrind "skins" require as much memory as MemCheck? Thanks in advance for any help. Ed |