|
From: Lucas B. <bra...@re...> - 2004-08-04 11:26:03
|
Hi Nicholas: >> 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? No, it is not allocating that big. When I run my application without valgrind, every thing works fine, ie, VM not kills it. May be a library I'm using... I gonna check it out. I'm using libxml2 2.6.6, gdbm 1.8.0 and libpam 0.7.5 (among glibc, libz and libpthread). >> 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. I've tried with --tool=memcheck and I've got the same results, so I downgrade back to 2.0.0. thanks a lot for you answer. bests regards -- []'s Lucas Brasilino bra...@re... http://www.recife.pe.gov.br Emprel - Empresa Municipal de Informatica (pt_BR) Municipal Computing Enterprise (en_US) Recife - Pernambuco - Brasil Fone: +55-81-34167078 |