From a1bfeb7704061a7e9ebf2425ed357973a56ca6c6 Mon Sep 17 00:00:00 2001 From: Bart Van Assche Date: Thu, 10 Dec 2009 17:58:46 +0000 Subject: [PATCH] Made the description of DRD_TRACE_VAR(), ANNOTATE_TRACE_MEMORY() and VG_USERREQ__DRD_START_TRACE_ADDR more clear. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10965 --- drd/docs/drd-manual.xml | 28 ++++++++++++++++++++-------- 1 file changed, 20 insertions(+), 8 deletions(-) diff --git a/drd/docs/drd-manual.xml b/drd/docs/drd-manual.xml index 318a750b12..076e084019 100644 --- a/drd/docs/drd-manual.xml +++ b/drd/docs/drd-manual.xml @@ -923,14 +923,26 @@ available macros and client requests are: - The macros DRD_TRACE_VAR(x), - ANNOTATE_TRACE_MEMORY(&x) - and the corresponding client request - VG_USERREQ__DRD_START_TRACE_ADDR. Trace all - load and store activity on the specified address range. When DRD reports - a data race on a specified variable, and it's not immediately clear - which source code statements triggered the conflicting accesses, it can - be very helpful to trace all activity on the offending memory location. + The macro DRD_TRACE_VAR(x). Trace all load and store + activity for the address range starting at &x and + occupying sizeof(x) bytes. When DRD reports a data + race on a specified variable, and it's not immediately clear which + source code statements triggered the conflicting accesses, it can be + very helpful to trace all activity on the offending memory location. + + + + + The macro ANNOTATE_TRACE_MEMORY(&x). Trace all + load and store activity that touches at least the single byte at the + address &x. + + + + + The client request VG_USERREQ__DRD_START_TRACE_ADDR, + which allows to trace all load and store activity for the specified + address range. -- 2.47.2