From: Bart Van Assche Date: Wed, 22 Jul 2009 10:34:55 +0000 (+0000) Subject: Updated documentation related to the --read-var-info flag. X-Git-Tag: svn/VALGRIND_3_5_0~327 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=78e3a1549a9d5b1898ebe688278faace61f1be57;p=thirdparty%2Fvalgrind.git Updated documentation related to the --read-var-info flag. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10521 --- diff --git a/coregrind/m_main.c b/coregrind/m_main.c index 2ba71a89f2..40aecc8d76 100644 --- a/coregrind/m_main.c +++ b/coregrind/m_main.c @@ -137,7 +137,8 @@ static void usage_NORETURN ( Bool debug_help ) " 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" diff --git a/drd/docs/drd-manual.xml b/drd/docs/drd-manual.xml index 42f4074500..caf6eb7a89 100644 --- a/drd/docs/drd-manual.xml +++ b/drd/docs/drd-manual.xml @@ -456,20 +456,6 @@ behavior of the DRD tool itself: - - - - - - - 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. - - -