|
From: Nicholas N. <nj...@ca...> - 2004-08-03 18:17:01
|
On Tue, 3 Aug 2004, Lucas Brasilino wrote: > I'm trying to debug some memory leaks using valgrind 2.0.0 > and options "-v --leak-check=yes" but it is ending with: > > ==<PID>== Warning: set address range perms: large range 538090744, a 0, v 0 That happens when Valgrind sees a big allocation or deallocation via malloc(), free, brk(), mmap(), munmap(), etc. It's not necessarily a problem, but it is a bit suspicious -- is your program likely to be allocating or deallocating 530+ MB in one hit, either directly or via a library? > And kernel VM (2.4.20-31.9) ends valgrind with "out of memory". > When I run the application without valgrind, it works just fine. > Anybody knows something about is annoying issue? You could try using --tool=addrcheck, which uses less memory than --tool=memcheck (but also does less thorough checking) You could also try valgrind 2.1.2, to see if that acts any different. N |