From: Nicholas Nethercote <njn@valgrind.org>
Date: Tue, 16 Aug 2005 03:42:44 +0000 (+0000)
Subject: minor fixes (probably not worth backporting)
X-Git-Tag: svn/VALGRIND_3_1_0~584
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=39589630bfd3eeacc1301a813e724da4cb525677;p=thirdparty%2Fvalgrind.git

minor fixes (probably not worth backporting)



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@4434
---

diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index 7c4db3d9e4..f7b2dccc7c 100644
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -14,8 +14,8 @@ command line.</para>
        xreflabel="Kinds of bugs that Memcheck can find">
 <title>Kinds of bugs that Memcheck can find</title>
 
-<para>Memcheck is Valgrind-1.0.X's checking mechanism bundled up
-into a tool.  All reads and writes of memory are checked, and
+<para>Memcheck is Valgrind's heavyweight memory checking
+tool.  All reads and writes of memory are checked, and
 calls to malloc/new/free/delete are intercepted. As a result,
 Memcheck can detect the following problems:</para>
 
@@ -142,8 +142,7 @@ Memcheck can detect the following problems:</para>
     [default]</para>
     <para><computeroutput>--workaround-gcc296-bugs=yes</computeroutput></para>
     <para>When enabled, assume that reads and writes some small
-    distance below the stack pointer
-    <computeroutput>%esp</computeroutput> are due to bugs in gcc
+    distance below the stack pointer are due to bugs in gcc
     2.96, and does not report them.  The "small distance" is 256
     bytes by default.  Note that gcc 2.96 is the default compiler
     on some popular Linux distributions (RedHat 7.X, Mandrake)
@@ -234,10 +233,10 @@ malloc'd.</para>
 
 <para>In this example, Memcheck can't identify the address.
 Actually the address is on the stack, but, for some reason, this
-is not a valid stack address -- it is below the stack pointer,
-<literal>%esp</literal>, and that isn't allowed.  In this
+is not a valid stack address -- it is below the stack pointer
+and that isn't allowed.  In this
 particular case it's probably caused by gcc generating invalid
-code, a known bug in various flavours of gcc.</para>
+code, a known bug in various versions of gcc.</para>
 
 <para>Note that Memcheck only tells you that your program is
 about to access memory at an illegal address.  It can't stop the
@@ -853,7 +852,7 @@ bits, only consult them.</para>
   <listitem>
     <para>When the stack pointer register
     (<literal>SP</literal>) moves up or down,
-    <literal>A</literal> bits are set.  The rule is that the area
+    A bits are set.  The rule is that the area
     from <literal>SP</literal> up to the base of the stack is
     marked as accessible, and below <literal>SP</literal> is
     inaccessible.  (If that sounds illogical, bear in mind that