|
From: <sv...@va...> - 2006-11-03 19:54:47
|
Author: njn
Date: 2006-11-03 19:54:45 +0000 (Fri, 03 Nov 2006)
New Revision: 6346
Log:
Fix a man page bug.
MERGED FROM TRUNK
Modified:
tags/VALGRIND_3_2_1/memcheck/docs/mc-manual.xml
Modified: tags/VALGRIND_3_2_1/memcheck/docs/mc-manual.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- tags/VALGRIND_3_2_1/memcheck/docs/mc-manual.xml 2006-11-03 19:54:21 U=
TC (rev 6345)
+++ tags/VALGRIND_3_2_1/memcheck/docs/mc-manual.xml 2006-11-03 19:54:45 U=
TC (rev 6346)
@@ -191,11 +191,10 @@
</term>
<listitem>
<para>Controls whether <constant>memcheck</constant> detects
- dangerous uses of undefined value errors. When
- <varname>yes</varname>, Memcheck behaves like Addrcheck, a lightwe=
ight
- memory-checking tool that used to be part of Valgrind, which didn'=
t
- detect undefined value errors. Use this option if you don't like
- seeing undefined value errors.
+ dangerous uses of undefined value errors. Set this to
+ <varname>no</varname> if you don't like seeing undefined value
+ errors; it also has the side effect of speeding
+ <constant>memcheck</constant> up somewhat.
</para>
</listitem>
</varlistentry>
|