|
From: Julian S. <js...@ac...> - 2008-03-25 11:04:32
|
> I've tried to insert VALGRIND_DO_LEAK_CHECK into program's main loop, > but eventually got false positive `definetly lost' blocks in this > place (there's no memleaks when program normally stops in valgrind's > report). > > The question is: > Does VALGRIND_DO_LEAK_CHECK work in ANY cases and I > should model this situation and report a bug, or there is yet some > cases memcheck can't handle? False positives are possible, but unlikely. The probability of a false positive increases as the address space gets more and more used, which is probably why you saw them. Anyway. It sounds like you maybe need to use Valgrind's Massif tool to find the cause of the allocations (--tool=massif). Make sure to use Massif in Valgrind version 3.3.0. Some documentation is here: http://www.valgrind.org/docs/manual/ms-manual.html J |