|
From: <sv...@va...> - 2009-12-10 17:59:02
|
Author: bart
Date: 2009-12-10 17:58:46 +0000 (Thu, 10 Dec 2009)
New Revision: 10965
Log:
Made the description of DRD_TRACE_VAR(), ANNOTATE_TRACE_MEMORY() and
VG_USERREQ__DRD_START_TRACE_ADDR more clear.
Modified:
trunk/drd/docs/drd-manual.xml
Modified: trunk/drd/docs/drd-manual.xml
===================================================================
--- trunk/drd/docs/drd-manual.xml 2009-12-03 14:35:15 UTC (rev 10964)
+++ trunk/drd/docs/drd-manual.xml 2009-12-10 17:58:46 UTC (rev 10965)
@@ -923,18 +923,30 @@
</listitem>
<listitem>
<para>
- The macros <literal>DRD_TRACE_VAR(x)</literal>,
- <literal>ANNOTATE_TRACE_MEMORY(&x)</literal>
- and the corresponding client request
- <varname>VG_USERREQ__DRD_START_TRACE_ADDR</varname>. 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 <literal>DRD_TRACE_VAR(x)</literal>. Trace all load and store
+ activity for the address range starting at <literal>&x</literal> and
+ occupying <literal>sizeof(x)</literal> 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.
</para>
</listitem>
<listitem>
<para>
+ The macro <literal>ANNOTATE_TRACE_MEMORY(&x)</literal>. Trace all
+ load and store activity that touches at least the single byte at the
+ address <literal>&x</literal>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The client request <varname>VG_USERREQ__DRD_START_TRACE_ADDR</varname>,
+ which allows to trace all load and store activity for the specified
+ address range.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
The client
request <varname>VG_USERREQ__DRD_STOP_TRACE_ADDR</varname>. Do no longer
trace load and store activity for the specified address range.
|