|
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. |