From: Julian Seward Date: Fri, 12 May 2006 23:12:30 +0000 (+0000) Subject: Increase number of unsuppressed errors shown before cutoff by a factor X-Git-Tag: svn/VALGRIND_3_2_0~64 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0eb39e5af3d09e5240bb15dbbe771c934723646e;p=thirdparty%2Fvalgrind.git 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 758df25194..e77a30e712 100644 --- 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 f33375676b..83aeee6410 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -333,10 +333,10 @@ root cause of the problem. 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 m_errormgr.c and can be increased if necessary.