|
From: Nicholas N. <nj...@ca...> - 2004-08-04 14:35:46
|
On Wed, 4 Aug 2004, Lucas Brasilino wrote: >> 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. Well, Memcheck more than doubles memory usage, so not running out of memory normally doesn't indicate much. > 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). It's potentially a valgrind bug. It would be great if you could isolate a test case and send us it. >> 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. Did --tool=addrcheck help? N |