More documentation updates.

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

diff --git a/drd/Testing.txt b/drd/Testing.txt
index 1fdd1fdea6b2685a5e0cf295935910b13e3c8d88..d2b4cf25f791283c61eeed5e0eb611b75b83352c 100644 (file)
--- a/drd/Testing.txt
+++ b/drd/Testing.txt
@@ -41,16 +41,16 @@ How to test DRD
 
 9. Test whether DRD works with standard KDE applications and whether it does
    not print any false positives. Test this both with KDE3 and KDE4.
-     ./vg-in-place --tool=drd --var-info=yes kate
-     ./vg-in-place --tool=drd --var-info=yes --check-stack-var=yes kate
-     ./vg-in-place --tool=drd --var-info=yes --trace-children=yes knode
-     ./vg-in-place --tool=drd --var-info=yes --check-stack-var=yes --trace-children=yes knode
-     ./vg-in-place --tool=drd --var-info=yes --check-stack-var=yes /usr/bin/designer
+     ./vg-in-place --tool=drd --read-var-info=yes kate
+     ./vg-in-place --tool=drd --read-var-info=yes --check-stack-var=yes kate
+     ./vg-in-place --tool=drd --read-var-info=yes --trace-children=yes knode
+     ./vg-in-place --tool=drd --read-var-info=yes --check-stack-var=yes --trace-children=yes knode
+     ./vg-in-place --tool=drd --read-var-info=yes --check-stack-var=yes /usr/bin/designer
 
 10. Test whether DRD works with standard GNOME applications. Expect
    race reports triggered by ORBit_RootObject_duplicate() and after
    having closed the GNOME terminal window:
-     ./vg-in-place --tool=drd --var-info=yes --trace-children=yes gnome-terminal
+     ./vg-in-place --tool=drd --read-var-info=yes --trace-children=yes gnome-terminal
 
 11. Rerun the GraphicsMagick test suite:
     1. Recompile gcc via drd/scripts/download-and-build-gcc.
@@ -68,7 +68,7 @@ How to test DRD
        cd GraphicsMagick
        ./configure
        export OMP_NUM_THREADS=4
-       make -j2 -s MEMCHECK="$HOME/software/valgrind/vg-in-place --tool=drd --check-stack-var=yes --var-info=yes --quiet" check
+       make -j2 -s MEMCHECK="$HOME/software/valgrind/vg-in-place --tool=drd --check-stack-var=yes --read-var-info=yes --quiet" check
     5. Expected result: 776 tests / 23 expected failures / 147m24s user time
        on a E8400 CPU @ 3 GHz.
 

diff --git a/drd/docs/drd-manual.xml b/drd/docs/drd-manual.xml
index caf6eb7a89da94578b855d55cb1e626f95cb099c..6966439b802a1bc25dbd01a69cef2c29c56ce014 100644 (file)
--- a/drd/docs/drd-manual.xml
+++ b/drd/docs/drd-manual.xml
@@ -584,7 +584,7 @@ Below you can find an example of a message printed by DRD when it
 detects a data race:
 </para>
 <programlisting><![CDATA[
-$ valgrind --tool=drd --var-info=yes drd/tests/rwlock_race
+$ valgrind --tool=drd --read-var-info=yes drd/tests/rwlock_race
 ...
 ==9466== Thread 3:
 ==9466== Conflicting load by thread 3 at 0x006020b8 size 4
@@ -652,7 +652,7 @@ The above report has the following meaning:
       displayed. For dynamically allocated data the allocation call
       stack is shown. For static variables and stack variables the
       allocation context is only shown when the option
-      <computeroutput>--var-info=yes</computeroutput> has been
+      <computeroutput>--read-var-info=yes</computeroutput> has been
       specified. Otherwise DRD will print <computeroutput>Allocation
       context: unknown</computeroutput>.
     </para>
@@ -1231,7 +1231,7 @@ not been declared private. DRD will print the following error message
 for the above code:
 </para>
 <programlisting><![CDATA[
-$ valgrind --tool=drd --check-stack-var=yes --var-info=yes drd/tests/omp_matinv 3 -t 2 -r
+$ valgrind --tool=drd --check-stack-var=yes --read-var-info=yes drd/tests/omp_matinv 3 -t 2 -r
 ...
 Conflicting store by thread 1/1 at 0x7fefffbc4 size 4
    at 0x4014A0: gj.omp_fn.0 (omp_matinv.c:203)
@@ -1353,7 +1353,7 @@ effect on the execution time of client programs are as follows:
       between 1.1 and 3.6 times more memory will be needed compared to
       a native run of the client program. More memory will be needed
       if loading debug information has been enabled
-      (<literal>--var-info=yes</literal>).
+      (<literal>--read-var-info=yes</literal>).
     </para>
   </listitem>
   <listitem>