|
From: Duncan S. <bal...@fr...> - 2006-03-16 22:06:58
|
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. |
|
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 > |
|
From: <dom...@fr...> - 2006-03-17 07:29:38
|
You can use 'valgrind --error-limit=3Dno' if you wanted to run without limitation on number of errors. -- Dominique Quoting Bryan Meredith <om...@br...>: > 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 repositor= y of a > few days ago) > > > > valgrind --tool=3Dmemcheck --show-reachable=3Dyes --leak-check=3Dyes > --db-attach=3Dyes ./program > > > > a total of four errors were reported. Then, after a few hours of run= ning, > this message > > was printed: > > > > =3D=3D26861=3D=3D > > =3D=3D26861=3D=3D More than 100000 total errors detected. I'm not re= porting any > more. > > =3D=3D26861=3D=3D Final error counts will be inaccurate. Go fix your= program! > > =3D=3D26861=3D=3D Rerun with --error-limit=3Dno to disable this cutof= f. Note > > =3D=3D26861=3D=3D that errors may occur in your program without prior= warning from > > =3D=3D26861=3D=3D Valgrind, because errors are no longer being displa= yed. > > =3D=3D26861=3D=3D > > > > 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 la= nguage > > that extends applications into web and mobile media. Attend the live > webcast > > and join the prime developer group breaking into this new coding terr= itory! > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&d= at=3D121642 > > _______________________________________________ > > Valgrind-users mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting lang= uage > that extends applications into web and mobile media. Attend the live we= bcast > and join the prime developer group breaking into this new coding territ= ory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > -- |
|
From: Duncan S. <bal...@fr...> - 2006-03-17 12:05:32
|
> 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. D'oh! Yes, that's it: there's an overlapping memcpy that's called many times, but only reported once. The annoying thing is that there's not much I can do about it: it's a compiler bug (the memcpy is generated by the compiler - it should be generating memmove; this has been sitting in gcc bugzilla for a while). I will use --error-limit=no, as suggested by Dominique. Thanks for your help, Duncan. |
|
From: Geoff A. <gal...@nc...> - 2006-03-17 16:17:38
|
Duncan, Can't you supply a suppression for the error? Geoff Alexander ----- Original Message ----- From: "Duncan Sands" <bal...@fr...> To: <val...@li...> Cc: "Bryan Meredith" <om...@br...> Sent: Friday, March 17, 2006 7:05 AM Subject: Re: [Valgrind-users] "More than 100000 total errors detected" - but only four reported! >> 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. > > D'oh! Yes, that's it: there's an overlapping memcpy that's called many > times, but only reported once. The annoying thing is that there's not > much I can do about it: it's a compiler bug (the memcpy is generated by > the compiler - it should be generating memmove; this has been sitting > in gcc bugzilla for a while). I will use --error-limit=no, as suggested > by Dominique. > > Thanks for your help, > > 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 > |