]> git.ipfire.org Git - thirdparty/valgrind.git/commit
Made the error reporting behavior of DRD similar to that of other
authorBart Van Assche <bvanassche@acm.org>
Mon, 27 Jul 2009 14:04:46 +0000 (14:04 +0000)
committerBart Van Assche <bvanassche@acm.org>
Mon, 27 Jul 2009 14:04:46 +0000 (14:04 +0000)
commit3770e93570884e513e765e4b875a084f375ef2c4
tree989f4b657aa6296c8e3c8c3e2594969a893bfa1a
parent2919d9219170e3d63a4d7e89851541d209f47157
Made the error reporting behavior of DRD similar to that of other
Valgrind tools: if the same kind of error has been detected a second
time with an identical call stack, count it as an error but do not print
it a second time. The total number of detected errors remains unchanged
but the number of error contexts is now reported correctly.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10633
drd/drd_error.c
drd/tests/bar_bad.stderr.exp
drd/tests/omp_matinv_racy.stderr.exp
drd/tests/pth_barrier2.stderr.exp
drd/tests/pth_barrier3.stderr.exp
drd/tests/tc09_bad_unlock.stderr.exp
drd/tests/tc09_bad_unlock.stderr.exp-glibc2.8
drd/tests/tc23_bogus_condwait.stderr.exp-darwin
drd/tests/tc23_bogus_condwait.stderr.exp-linux-ppc
drd/tests/tc23_bogus_condwait.stderr.exp-linux-x86
drd/tests/thread_name.stderr.exp