RE: [Valgrind-users] Effect of --error-limit=no on performance

[Nicholas N. <nj...@cs...>]

On Wed, 29 Mar 2006, Yeshurun, Meir wrote:

> However, the "I'm not reporting anymore" message usually appears when
> the exact same error is executed many times (e.g. an error that happens
> to be inside a loop). According to your reply, using --error-limit=no in
> this case shouldn't be a problem. It should only be a problem when
> you're getting a huge log file with many different call stacks. Did I
> understand correctly?

That sounds right.  As the manual says:

  When enabled, Valgrind stops reporting errors after 100000 in total, or
  1000 different ones, have been seen. This is to stop the error tracking
  machinery from becoming a huge performance overhead in programs with many
  errors.

Maybe the 100000 total limit isn't important and could be dropped, for the 
reasons discussed above.

Nick