New options for Memcheck, --malloc-fill=<hexnumber> and
--fill-free=<hexnumber>, which cause malloc'd(etc) and free'd(etc)
blocks to be filled with the specified value. This can apparently be
useful for shaking out hard-to-track-down memory corruption. The
definedness/addressability of said areas is not affected -- only the
contents. Documentation to follow.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7259 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/memcheck/mc_include.h b/memcheck/mc_include.h
index c731271..c48e481 100644
--- a/memcheck/mc_include.h
+++ b/memcheck/mc_include.h
@@ -282,6 +282,15 @@
* default: YES */
extern Bool MC_(clo_undef_value_errors);
+/* Fill malloc-d/free-d client blocks with a specific value? -1 if
+ not, else 0x00 .. 0xFF indicating the fill value to use. Can be
+ useful for causing programs with bad heap corruption to fail in
+ more repeatable ways. Note that malloc-filled and free-filled
+ areas are still undefined and noaccess respectively. This merely
+ causes them to contain the specified values. */
+extern Int MC_(clo_malloc_fill);
+extern Int MC_(clo_free_fill);
+
/*------------------------------------------------------------*/
/*--- Instrumentation ---*/