|
From: <sv...@va...> - 2009-07-22 10:35:03
|
Author: bart
Date: 2009-07-22 11:34:55 +0100 (Wed, 22 Jul 2009)
New Revision: 10521
Log:
Updated documentation related to the --read-var-info flag.
Modified:
trunk/coregrind/m_main.c
trunk/drd/docs/drd-manual.xml
Modified: trunk/coregrind/m_main.c
===================================================================
--- trunk/coregrind/m_main.c 2009-07-22 09:26:21 UTC (rev 10520)
+++ trunk/coregrind/m_main.c 2009-07-22 10:34:55 UTC (rev 10521)
@@ -137,7 +137,8 @@
" handle non-standard kernel variants\n"
" --read-var-info=yes|no read debug info on stack and global variables\n"
" and use it to print better error messages in\n"
-" tools that make use of it (Memcheck, Helgrind)\n"
+" tools that make use of it (Memcheck, Helgrind,\n"
+" DRD)\n"
"\n"
" user options for Valgrind tools that report errors:\n"
" --xml=yes emit error output in XML (some tools only)\n"
Modified: trunk/drd/docs/drd-manual.xml
===================================================================
--- trunk/drd/docs/drd-manual.xml 2009-07-22 09:26:21 UTC (rev 10520)
+++ trunk/drd/docs/drd-manual.xml 2009-07-22 10:34:55 UTC (rev 10521)
@@ -456,20 +456,6 @@
</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term>
- <option><![CDATA[--read-var-info=<yes|no> [default: no]]]></option>
- </term>
- <listitem>
- <para>
- Display the names of global, static and stack variables when a
- data race is reported. While this information can be very
- helpful, it is not loaded into memory by default. This is
- because for big programs reading in all debug information at
- once may cause an out of memory error.
- </para>
- </listitem>
- </varlistentry>
</variablelist>
<!-- end of xi:include in the manpage -->
|