From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Date: Sat, 15 Sep 2018 16:00:57 +0000 (+0200)
Subject: Do not mention VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE to bypass shared memory... 
X-Git-Tag: VALGRIND_3_14_0~22
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=97365bada64c27a40004c55793ff8988e59adf35;p=thirdparty%2Fvalgrind.git

Do not mention VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE to bypass shared memory definedness false positive

as when the error is reported (e.g. conditional jump), it is not
known anymore that this originates from which memory range.
---

diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index 514d63581f..eb1dfab272 100644
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -1581,8 +1581,7 @@ mapping.  The bypass for these false positives is to use Memcheck's client
 requests <varname>VALGRIND_MAKE_MEM_DEFINED</varname> and
 <varname>VALGRIND_MAKE_MEM_UNDEFINED</varname> to inform
 Memcheck about what your program does (or what another process does)
-to these shared memory mappings. Alternatively, you can also use
-<varname>VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE</varname>.
+to these shared memory mappings.
 </para>
 
 </sect2>