Terminology change: previously in Memcheck we had the four states:

   noaccess, writable, readable, other

Now they are:

   noaccess, undefined, defined, partdefined

As a result, the following names:

   make_writable, make_readable,
   check_writable, check_readable, check_defined

have become:

   make_mem_undefined, make_mem_defined,
   check_mem_is_addressable, check_mem_is_defined, check_value_is_defined

(and likewise for the upper-case versions for client request macros).
The old MAKE_* and CHECK_* macros still work for backwards compatibility.

This is much better, because the old names were subtly misleading.  For
example:

  - "readable" really meant "readable and writable".
  - "writable" really meant "writable and maybe readable, depending on how
    the read value is used".
  - "check_writable" really meant "check writable or readable"

The new names avoid these problems.

The recently-added macro which was called MAKE_DEFINED is now
MAKE_MEM_DEFINED_IF_ADDRESSABLE.

I also corrected the spelling of "addressable" in numerous places in
memcheck.h.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5802 a5019735-40e9-0310-863c-91ae7b9d1cf9

1 files changed, 1 insertions, 1 deletions

diff --git a/include/valgrind.h b/include/valgrind.h
index e92c58a1c..073d7dd41 100644
--- a/include/valgrind.h
+++ b/include/valgrind.h
@@ -2433,7 +2433,7 @@ VALGRIND_PRINTF_BACKTRACE(const char *format, ...)
    
    If you're allocating memory via superblocks, and then handing out small
    chunks of each superblock, if you don't have redzones on your small
-   blocks, it's worth marking the superblock with VALGRIND_MAKE_NOACCESS
+   blocks, it's worth marking the superblock with VALGRIND_MAKE_MEM_NOACCESS
    when it's created, so that block overruns are detected.  But if you can
    put redzones on, it's probably better to not do this, so that messages
    for small overruns are described in terms of the small block rather than