|
From: Sergei T. <sl...@in...> - 2008-03-24 19:34:46
|
Hello! I extensively use valgrind --tool=memcheck. And once upon a time I've got long running program merely consuming memory (just leaky), so valgrind dies of OOM. 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? Thanks! |