diff options
| author | njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> | 2006-10-18 21:50:26 +0000 |
|---|---|---|
| committer | njn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9> | 2006-10-18 21:50:26 +0000 |
| commit | 0fc5cbd2f87dfe72cfc6333dd0f1c900364f66d6 (patch) | |
| tree | 90b9f1772039c39840c2173ee7b8590fac6b96fc /include | |
| parent | a087148a278b59856ec2247361d1902524c68f95 (diff) | |
| download | valgrind-0fc5cbd2f87dfe72cfc6333dd0f1c900364f66d6.tar.gz | |
Move VG_BUGS_TO to pub_tool_basics.h so that Nulgrind need not import
pub_tool_libcassert.h.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6320 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'include')
| -rw-r--r-- | include/pub_tool_tooliface.h | 2 | ||||
| -rw-r--r-- | include/valgrind.h | 18 |
2 files changed, 10 insertions, 10 deletions
diff --git a/include/pub_tool_tooliface.h b/include/pub_tool_tooliface.h index 89128b2f3..c28010d4a 100644 --- a/include/pub_tool_tooliface.h +++ b/include/pub_tool_tooliface.h @@ -32,7 +32,7 @@ #define __PUB_TOOL_TOOLIFACE_H #include "pub_tool_errormgr.h" // for Error, Supp -#include "libvex.h" // for VexGuestLayout +#include "libvex.h" // for all Vex stuff /* ------------------------------------------------------------------ */ /* The interface version */ diff --git a/include/valgrind.h b/include/valgrind.h index ae82e25c9..dafc0d910 100644 --- a/include/valgrind.h +++ b/include/valgrind.h @@ -3715,15 +3715,15 @@ VALGRIND_PRINTF_BACKTRACE(const char *format, ...) for calloc(). Put it immediately after the point where a block is allocated. - 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_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 - the superblock (but if you have a big overrun that skips over a redzone, - you could miss an error this way). See memcheck/tests/custom_alloc.c - for an example. + If you're using Memcheck: 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_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 the superblock (but if you have a big overrun + that skips over a redzone, 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 -- |