|
From: Michael S. <ms...@vm...> - 2011-02-04 21:24:22
|
Hello, First time contributor, excuse me if I don't know local conventions. I spotted this typo while reading the printed version of the manual. Cheers, Michael Snyder bash-3.2$ diff -up mc-manual.xml~ mc-manual.xml --- mc-manual.xml~ 2010-10-20 13:19:25.000000000 -0700 +++ mc-manual.xml 2011-02-04 13:21:27.000000000 -0800 @@ -263,7 +263,7 @@ so it can know exactly whether or not th legitimate or not. Here, this test program has freed the same block twice. As with the illegal read/write errors, Memcheck attempts to make sense of the address freed. If, as here, the address is one -which has previously been freed, you wil be told that -- making +which has previously been freed, you will be told that -- making duplicate frees of the same block easy to spot. You will also get this message if you try to free a pointer that doesn't point to the start of a heap block.</para> |
|
From: Michael S. <ms...@vm...> - 2011-02-08 18:32:51
|
Here's another, from context it seems like "or" was meant to be "of". bash-3.2$ diff -up mc-manual.xml~ mc-manual.xml --- mc-manual.xml~ 2011-02-04 13:21:27.000000000 -0800 +++ mc-manual.xml 2011-02-04 13:45:38.000000000 -0800 @@ -1085,7 +1085,7 @@ location. We now consider the latter qu 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.</para> |