|
From: Ivo R. <iv...@iv...> - 2016-12-08 10:21:34
|
2016-12-07 18:39 GMT+01:00 Gregory Czajkowski <gcf...@gm...>: > I have processes near 256GB, need to run valgrind to determine why, but it > runs out of memory ~60GB > > > ==15336== Valgrind's memory management: out of memory: > > ==15336== newSuperblock's request for 4194304 bytes failed. > > ==15336== 62,289,825,792 bytes have already been mmap-ed ANONYMOUS. > > ==15336== Valgrind cannot continue. Sorry. > > ==15336== more, depending on the tool. On a 64-bit machine, Valgrind > ==15336== should be able to make use of up 32GB memory. > > How can it's limits be increased? > If you google around then you'll hit: http://stackoverflow.com/questions/8644234/why-is-valgrind-limited-to-32-gb-on-64-bit-architectures http://valgrind.10908.n7.nabble.com/increase-32G-limit-td43507.html This topic was also recently discussed on Valgrind user's list. Kind regards, I. |