zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-04 02:18:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

More documentation updates.

Browse Source 
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10525
This commit is contained in:
Bart Van Assche 2009-07-22 18:13:21 +00:00
parent 976d2fe5d2
commit 5f2fb765ab
2 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
drd/Testing.txt
View File

@ -41,16 +41,16 @@ How to test DRD
9. Test whether DRD works with standard KDE applications and whether it does
not print any false positives. Test this both with KDE3 and KDE4.
./vg-in-place --tool=drd --var-info=yes kate
./vg-in-place --tool=drd --var-info=yes --check-stack-var=yes kate
./vg-in-place --tool=drd --var-info=yes --trace-children=yes knode
./vg-in-place --tool=drd --var-info=yes --check-stack-var=yes --trace-children=yes knode
./vg-in-place --tool=drd --var-info=yes --check-stack-var=yes /usr/bin/designer
./vg-in-place --tool=drd --read-var-info=yes kate
./vg-in-place --tool=drd --read-var-info=yes --check-stack-var=yes kate
./vg-in-place --tool=drd --read-var-info=yes --trace-children=yes knode
./vg-in-place --tool=drd --read-var-info=yes --check-stack-var=yes --trace-children=yes knode
./vg-in-place --tool=drd --read-var-info=yes --check-stack-var=yes /usr/bin/designer
10. Test whether DRD works with standard GNOME applications. Expect
race reports triggered by ORBit_RootObject_duplicate() and after
having closed the GNOME terminal window:
./vg-in-place --tool=drd --var-info=yes --trace-children=yes gnome-terminal
./vg-in-place --tool=drd --read-var-info=yes --trace-children=yes gnome-terminal
11. Rerun the GraphicsMagick test suite:
1. Recompile gcc via drd/scripts/download-and-build-gcc.
@ -68,7 +68,7 @@ How to test DRD
cd GraphicsMagick
./configure
export OMP_NUM_THREADS=4
make -j2 -s MEMCHECK="$HOME/software/valgrind/vg-in-place --tool=drd --check-stack-var=yes --var-info=yes --quiet" check
make -j2 -s MEMCHECK="$HOME/software/valgrind/vg-in-place --tool=drd --check-stack-var=yes --read-var-info=yes --quiet" check
5. Expected result: 776 tests / 23 expected failures / 147m24s user time
on a E8400 CPU @ 3 GHz.

8
drd/docs/drd-manual.xml
View File

@ -584,7 +584,7 @@ Below you can find an example of a message printed by DRD when it
detects a data race:
</para>
<programlisting><![CDATA[
$ valgrind --tool=drd --var-info=yes drd/tests/rwlock_race
$ valgrind --tool=drd --read-var-info=yes drd/tests/rwlock_race
...
==9466== Thread 3:
==9466== Conflicting load by thread 3 at 0x006020b8 size 4
@ -652,7 +652,7 @@ The above report has the following meaning:
displayed. For dynamically allocated data the allocation call
stack is shown. For static variables and stack variables the
allocation context is only shown when the option
<computeroutput>--var-info=yes</computeroutput> has been
<computeroutput>--read-var-info=yes</computeroutput> has been
specified. Otherwise DRD will print <computeroutput>Allocation
context: unknown</computeroutput>.
</para>
@ -1231,7 +1231,7 @@ not been declared private. DRD will print the following error message
for the above code:
</para>
<programlisting><![CDATA[
$ valgrind --tool=drd --check-stack-var=yes --var-info=yes drd/tests/omp_matinv 3 -t 2 -r
$ valgrind --tool=drd --check-stack-var=yes --read-var-info=yes drd/tests/omp_matinv 3 -t 2 -r
...
Conflicting store by thread 1/1 at 0x7fefffbc4 size 4
at 0x4014A0: gj.omp_fn.0 (omp_matinv.c:203)
@ -1353,7 +1353,7 @@ effect on the execution time of client programs are as follows:
between 1.1 and 3.6 times more memory will be needed compared to
a native run of the client program. More memory will be needed
if loading debug information has been enabled
(<literal>--var-info=yes</literal>).
(<literal>--read-var-info=yes</literal>).
</para>
</listitem>
<listitem>