|
From: <sv...@va...> - 2013-04-05 13:19:21
|
mjw 2013-04-05 14:19:12 +0100 (Fri, 05 Apr 2013)
New Revision: 13363
Log:
Fix double 'the the' in documentation.
Modified files:
trunk/cachegrind/docs/cg-manual.xml
trunk/docs/xml/manual-core-adv.xml
trunk/drd/docs/drd-manual.xml
trunk/exp-sgcheck/docs/sg-manual.xml
trunk/memcheck/docs/mc-manual.xml
trunk/memcheck/docs/mc-tech-docs.xml
Modified: trunk/cachegrind/docs/cg-manual.xml (+2 -2)
===================================================================
--- trunk/cachegrind/docs/cg-manual.xml 2013-04-05 13:53:16 +01:00 (rev 13362)
+++ trunk/cachegrind/docs/cg-manual.xml 2013-04-05 14:19:12 +01:00 (rev 13363)
@@ -352,7 +352,7 @@
that event (e.g. the third row shows that
<computeroutput>strcmp()</computeroutput> contains no
instructions that write to memory). The name
-<computeroutput>???</computeroutput> is used if the the file name
+<computeroutput>???</computeroutput> is used if the file name
and/or function name could not be determined from debugging
information. If most of the entries have the form
<computeroutput>???:???</computeroutput> the program probably
@@ -1367,7 +1367,7 @@
</itemizedlist>
<para>Another thing worth noting is that results are very sensitive.
-Changing the size of the the executable being profiled, or the sizes
+Changing the size of the executable being profiled, or the sizes
of any of the shared libraries it uses, or even the length of their
file names, can perturb the results. Variations will be small, but
don't expect perfectly repeatable results if your program changes at
Modified: trunk/docs/xml/manual-core-adv.xml (+1 -1)
===================================================================
--- trunk/docs/xml/manual-core-adv.xml 2013-04-05 13:53:16 +01:00 (rev 13362)
+++ trunk/docs/xml/manual-core-adv.xml 2013-04-05 14:19:12 +01:00 (rev 13363)
@@ -1542,7 +1542,7 @@
The details are discussed below.</para>
<para><computeroutput>VALGRIND_GET_ORIG_FN</computeroutput>:
-once in the the wrapper, the first priority is
+once in the wrapper, the first priority is
to get hold of the address of the original (and any other supporting
information needed). This is stored in a value of opaque
type <computeroutput>OrigFn</computeroutput>.
Modified: trunk/exp-sgcheck/docs/sg-manual.xml (+1 -1)
===================================================================
--- trunk/exp-sgcheck/docs/sg-manual.xml 2013-04-05 13:53:16 +01:00 (rev 13362)
+++ trunk/exp-sgcheck/docs/sg-manual.xml 2013-04-05 14:19:12 +01:00 (rev 13363)
@@ -217,7 +217,7 @@
</listitem>
<listitem>
- <para>Coverage: SGCheck does not check whether the the areas read
+ <para>Coverage: SGCheck does not check whether the areas read
or written by system calls do overrun stack or global arrays. This
would be easy to add.</para>
</listitem>
Modified: trunk/memcheck/docs/mc-tech-docs.xml (+1 -1)
===================================================================
--- trunk/memcheck/docs/mc-tech-docs.xml 2013-04-05 13:53:16 +01:00 (rev 13362)
+++ trunk/memcheck/docs/mc-tech-docs.xml 2013-04-05 14:19:12 +01:00 (rev 13363)
@@ -848,7 +848,7 @@
<title>Introduction to UCode</title>
<para>UCode lies at the heart of the x86-to-x86 JITter. The
-basic premise is that dealing the the x86 instruction set head-on
+basic premise is that dealing with the x86 instruction set head-on
is just too darn complicated, so we do the traditional
compiler-writer's trick and translate it into a simpler,
easier-to-deal-with form.</para>
Modified: trunk/memcheck/docs/mc-manual.xml (+1 -1)
===================================================================
--- trunk/memcheck/docs/mc-manual.xml 2013-04-05 13:53:16 +01:00 (rev 13362)
+++ trunk/memcheck/docs/mc-manual.xml 2013-04-05 14:19:12 +01:00 (rev 13363)
@@ -821,7 +821,7 @@
bytes are marked as initialised.</para>
<para>Note that code that behaves in this way is in violation of
- the the ISO C/C++ standards, and should be considered broken. If
+ the ISO C/C++ standards, and should be considered broken. If
at all possible, such code should be fixed. This option should be
used only as a last resort.</para>
</listitem>
Modified: trunk/drd/docs/drd-manual.xml (+1 -1)
===================================================================
--- trunk/drd/docs/drd-manual.xml 2013-04-05 13:53:16 +01:00 (rev 13362)
+++ trunk/drd/docs/drd-manual.xml 2013-04-05 14:19:12 +01:00 (rev 13363)
@@ -497,7 +497,7 @@
Print stack usage at thread exit time. When a program creates a large
number of threads it becomes important to limit the amount of virtual
memory allocated for thread stacks. This option makes it possible to
- observe how much stack memory has been used by each thread of the the
+ observe how much stack memory has been used by each thread of the
client program. Note: the DRD tool itself allocates some temporary
data on the client thread stack. The space necessary for this
temporary data must be allocated by the client program when it
|