Increase number of unsuppressed errors shown before cutoff by a factor

of 100.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5895

diff --git a/coregrind/m_errormgr.c b/coregrind/m_errormgr.c
index 758df251948e4819809aaed1e2ae9bb5d9a7e422..e77a30e7127642893e09a77d0f670caddaf48184 100644 (file)
--- a/coregrind/m_errormgr.c
+++ b/coregrind/m_errormgr.c
@@ -60,7 +60,7 @@
 
 /* After this many total errors have been observed, stop collecting
    errors at all.  Counterpart to M_COLLECT_NO_ERRORS_AFTER_SHOWN. */
-#define M_COLLECT_NO_ERRORS_AFTER_FOUND 100000
+#define M_COLLECT_NO_ERRORS_AFTER_FOUND 10000000
 
 /* The list of error contexts found, both suppressed and unsuppressed.
    Initially empty, and grows as errors are detected. */

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index f33375676b22c532e2206e23045942401153163c..83aeee6410c7a19148c1faa1ac16fd7ad125e8ea 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -333,10 +333,10 @@ root cause of the problem.</para>
 expensive one and can become a significant performance overhead
 if your program generates huge quantities of errors.  To avoid
 serious problems, Valgrind will simply stop collecting
-errors after 1000 different errors have been seen, or 100000 errors
+errors after 1000 different errors have been seen, or 10000000 errors
 in total have been seen.  In this situation you might as well
 stop your program and fix it, because Valgrind won't tell you
-anything else useful after this.  Note that the 1000/100000 limits
+anything else useful after this.  Note that the 1000/10000000 limits
 apply after suppressed errors are removed.  These limits are
 defined in <filename>m_errormgr.c</filename> and can be increased
 if necessary.</para>