From: Julian Seward Date: Mon, 28 Feb 2011 10:26:42 +0000 (+0000) Subject: Fix minor documentation nits (Michael Snyder, msnyder@vmware.com) X-Git-Tag: svn/VALGRIND_3_7_0~652 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=47be27ff77df07abd04dfb25818228f449f5e8e2;p=thirdparty%2Fvalgrind.git Fix minor documentation nits (Michael Snyder, msnyder@vmware.com) git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11577 --- diff --git a/helgrind/docs/hg-manual.xml b/helgrind/docs/hg-manual.xml index 08ab3d5460..bbb3f562bf 100644 --- a/helgrind/docs/hg-manual.xml +++ b/helgrind/docs/hg-manual.xml @@ -229,7 +229,7 @@ Thread #1: lock order "0x7FEFFFAB0 before 0x7FEFFFA80" violated When there are more than two locks in the cycle, the error is equally serious. However, at present Helgrind does not show the locks involved, so as to avoid flooding you with information. That could be -fixed in future. For example, here is a an example involving a cycle +fixed in future. For example, here is an example involving a cycle of five locks from a naive implementation the famous Dining Philosophers problem (see helgrind/tests/tc14_laog_dinphils.c). @@ -262,7 +262,7 @@ are race-free is one of the central difficulties of threaded programming. Reliably detecting races is a difficult problem, and most -of Helgrind's internals are devoted to do dealing with it. +of Helgrind's internals are devoted to dealing with it. We begin with a simple example. diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml index a590d585a7..433e2e0558 100644 --- a/memcheck/docs/mc-manual.xml +++ b/memcheck/docs/mc-manual.xml @@ -1089,7 +1089,7 @@ location. We now consider the latter question. associated valid-value (V) bit. In addition, all bytes in memory, but not in the CPU, have an associated valid-address (A) bit. This indicates whether or not the program can legitimately read or write that -location. It does not give any indication of the validity or the data +location. It does not give any indication of the validity of the data at that location -- that's the job of the V bits -- only whether or not the location may be accessed.