It should be in the section on tools that replace malloc.
" size/blocks, full: profile current and cumulative\n"
" allocated size/blocks and freed size/blocks.\n"
" --xtree-memory-file=<file> xtree memory report file [xtmemory.kcg.%%p]\n"
+" --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]\n"
+" should calls to realloc with a size of 0\n"
+" free memory and return NULL or\n"
+" allocate/resize and return non-NULL\n"
"\n"
" uncommon user options for all Valgrind tools:\n"
" --fullpath-after= (with nothing after the '=')\n"
" attempt to avoid expensive address-space-resync operations\n"
" --max-threads=<number> maximum number of threads that valgrind can\n"
" handle [%d]\n"
-" --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]\n"
-" should calls to realloc with a size of 0\n"
-" free memory and return NULL or\n"
-" allocate/resize and return non-NULL\n"
"\n";
const HChar usage2[] =
size/blocks, full: profile current and cumulative
allocated size/blocks and freed size/blocks.
--xtree-memory-file=<file> xtree memory report file [xtmemory.kcg.%p]
+ --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
+ should calls to realloc with a size of 0
+ free memory and return NULL or
+ allocate/resize and return non-NULL
uncommon user options for all Valgrind tools:
--fullpath-after= (with nothing after the '=')
attempt to avoid expensive address-space-resync operations
--max-threads=<number> maximum number of threads that valgrind can
handle [500]
- --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
- should calls to realloc with a size of 0
- free memory and return NULL or
- allocate/resize and return non-NULL
user options for Nulgrind:
(none)
size/blocks, full: profile current and cumulative
allocated size/blocks and freed size/blocks.
--xtree-memory-file=<file> xtree memory report file [xtmemory.kcg.%p]
+ --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
+ should calls to realloc with a size of 0
+ free memory and return NULL or
+ allocate/resize and return non-NULL
uncommon user options for all Valgrind tools:
--fullpath-after= (with nothing after the '=')
attempt to avoid expensive address-space-resync operations
--max-threads=<number> maximum number of threads that valgrind can
handle [500]
- --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
- should calls to realloc with a size of 0
- free memory and return NULL or
- allocate/resize and return non-NULL
user options for Nulgrind:
(none)
size/blocks, full: profile current and cumulative
allocated size/blocks and freed size/blocks.
--xtree-memory-file=<file> xtree memory report file [xtmemory.kcg.%p]
+ --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
+ should calls to realloc with a size of 0
+ free memory and return NULL or
+ allocate/resize and return non-NULL
uncommon user options for all Valgrind tools:
--fullpath-after= (with nothing after the '=')
attempt to avoid expensive address-space-resync operations
--max-threads=<number> maximum number of threads that valgrind can
handle [500]
- --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
- should calls to realloc with a size of 0
- free memory and return NULL or
- allocate/resize and return non-NULL
user options for Nulgrind:
(none)
size/blocks, full: profile current and cumulative
allocated size/blocks and freed size/blocks.
--xtree-memory-file=<file> xtree memory report file [xtmemory.kcg.%p]
+ --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
+ should calls to realloc with a size of 0
+ free memory and return NULL or
+ allocate/resize and return non-NULL
uncommon user options for all Valgrind tools:
--fullpath-after= (with nothing after the '=')
attempt to avoid expensive address-space-resync operations
--max-threads=<number> maximum number of threads that valgrind can
handle [500]
- --realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no otherwise]
- should calls to realloc with a size of 0
- free memory and return NULL or
- allocate/resize and return non-NULL
user options for Nulgrind:
(none)