|
From: <sv...@va...> - 2009-07-22 09:26:28
|
Author: bart
Date: 2009-07-22 10:26:21 +0100 (Wed, 22 Jul 2009)
New Revision: 10520
Log:
Removed code for handling --read-var-info from DRD since the Valgrind core already interprets this flag.
Modified:
trunk/drd/drd_main.c
Modified: trunk/drd/drd_main.c
===================================================================
--- trunk/drd/drd_main.c 2009-07-22 07:30:37 UTC (rev 10519)
+++ trunk/drd/drd_main.c 2009-07-22 09:26:21 UTC (rev 10520)
@@ -110,7 +110,6 @@
else if VG_BOOL_CLO(arg, "--trace-segment", trace_segment) {}
else if VG_BOOL_CLO(arg, "--trace-semaphore", trace_semaphore) {}
else if VG_BOOL_CLO(arg, "--trace-suppr", trace_suppression) {}
- else if VG_BOOL_CLO(arg, "--read-var-info", DRD_(s_var_info)) {}
else if VG_BOOL_CLO(arg, "--var-info", DRD_(s_var_info)) {}
else if VG_INT_CLO (arg, "--exclusive-threshold", exclusive_threshold_ms) {}
else if VG_INT_CLO (arg, "--shared-threshold", shared_threshold_ms) {}
@@ -200,11 +199,6 @@
" is held longer than the specified time (in milliseconds).\n"
" --show-confl-seg=yes|no Show conflicting segments in race reports [yes].\n"
" --show-stack-usage=yes|no Print stack usage at thread exit time [no].\n"
-" --read-var-info=yes|no Display the names of global, static and\n"
-" stack variables when a race is reported on such a variable. This\n"
-" information is by default not displayed since for big programs\n"
-" reading in all debug information at once may cause an out of\n"
-" memory error [no].\n"
"\n"
" drd options for monitoring process behavior:\n"
" --trace-addr=<address> Trace all load and store activity for the.\n"
|