Do not mention VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE to bypass shared memory...

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 514d63581f1a79703132d059e317378d512dc96b..eb1dfab272e5f7dc3816f0d25b92f880c347dd4d 100644 (file)
--- 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>