summaryrefslogtreecommitdiff
path: root/include/valgrind.h
diff options
context:
space:
mode:
authornjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2006-06-02 22:32:02 +0000
committernjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2006-06-02 22:32:02 +0000
commit479db774b080e3eef41b2ebb94d67f82d5c1788e (patch)
treef7d635e1402351c706a3b05367e8ceb8d8e69afc /include/valgrind.h
parentbb3726515345b19ab72e877432cc1e75c9615869 (diff)
Add a helpful comment.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5949 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'include/valgrind.h')
-rw-r--r--include/valgrind.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/include/valgrind.h b/include/valgrind.h
index b5c8222b..82d9a78a 100644
--- a/include/valgrind.h
+++ b/include/valgrind.h
@@ -2442,6 +2442,11 @@ VALGRIND_PRINTF_BACKTRACE(const char *format, ...)
you could miss an error this way). See memcheck/tests/custom_alloc.c
for an example.
+ WARNING: if your allocator uses malloc() or 'new' to allocate
+ superblocks, rather than mmap() or brk(), this will not work properly --
+ you'll likely get assertion failures during leak detection. This is
+ because Valgrind doesn't like seeing overlapping heap blocks. Sorry.
+
Nb: block must be freed via a free()-like function specified
with VALGRIND_FREELIKE_BLOCK or mismatch errors will occur. */
#define VALGRIND_MALLOCLIKE_BLOCK(addr, sizeB, rzB, is_zeroed) \