|
From: Nicholas N. <nj...@cs...> - 2005-02-06 20:34:25
|
On Sun, 6 Feb 2005, Edward Moyse wrote: > 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" 2.2.0 does handle memory differently to 2.0.0, which can cause problems. Without any more info about how things go wrong, we can't give any help, though. The 12x figure is flat-out wrong; the expansion factor depends on a bunch of things. If you use 1GB, things will be pretty tight for Memcheck, which may be the problem. You could try Addrcheck, which uses less memory. N |