|
From: Bryan M. <om...@br...> - 2006-03-16 22:34:43
|
Duncan, Valgrind doesn't keep printing the same error time and time again. Your program may have only 4 errors but if each of them occurs 25000 times, Valgrind will stop with the message you have here. If you stopped execution early, Valgrind would report how many times each of those errors occurred. Hope this helps, Bryan "Brain Murders" Meredith Duncan Sands wrote: > While running valgrind valgrind-3.1.0RC1 (compiled from svn repository of a few days ago) > > valgrind --tool=memcheck --show-reachable=yes --leak-check=yes --db-attach=yes ./program > > a total of four errors were reported. Then, after a few hours of running, this message > was printed: > > ==26861== > ==26861== More than 100000 total errors detected. I'm not reporting any more. > ==26861== Final error counts will be inaccurate. Go fix your program! > ==26861== Rerun with --error-limit=no to disable this cutoff. Note > ==26861== that errors may occur in your program without prior warning from > ==26861== Valgrind, because errors are no longer being displayed. > ==26861== > > valgrind may have detected 100000 errors, but it didn't mention them! Any idea what's > going on here? > > Best wishes, > > Duncan. > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |