From: Paul Floyd Date: Fri, 9 Feb 2024 20:20:40 +0000 (+0100) Subject: command line help: move --realloc-zero-bytes-frees X-Git-Tag: VALGRIND_3_23_0~174 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=a13a10a569e9ad75c0dda2f83cf2afaf21035e37;p=thirdparty%2Fvalgrind.git command line help: move --realloc-zero-bytes-frees It should be in the section on tools that replace malloc. --- diff --git a/coregrind/m_main.c b/coregrind/m_main.c index bb4a0ca96..3015a533c 100644 --- a/coregrind/m_main.c +++ b/coregrind/m_main.c @@ -166,6 +166,10 @@ static void usage_NORETURN ( int need_help ) " size/blocks, full: profile current and cumulative\n" " allocated size/blocks and freed size/blocks.\n" " --xtree-memory-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" @@ -243,10 +247,6 @@ static void usage_NORETURN ( int need_help ) " attempt to avoid expensive address-space-resync operations\n" " --max-threads= 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[] = diff --git a/none/tests/cmdline1.stdout.exp b/none/tests/cmdline1.stdout.exp index 3b6c11609..ce3cdfcf5 100644 --- a/none/tests/cmdline1.stdout.exp +++ b/none/tests/cmdline1.stdout.exp @@ -79,6 +79,10 @@ usage: valgrind [options] prog-and-args size/blocks, full: profile current and cumulative allocated size/blocks and freed size/blocks. --xtree-memory-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 '=') @@ -154,10 +158,6 @@ usage: valgrind [options] prog-and-args attempt to avoid expensive address-space-resync operations --max-threads= 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) diff --git a/none/tests/cmdline1.stdout.exp-non-linux b/none/tests/cmdline1.stdout.exp-non-linux index e67183efe..45820cbbc 100644 --- a/none/tests/cmdline1.stdout.exp-non-linux +++ b/none/tests/cmdline1.stdout.exp-non-linux @@ -77,6 +77,10 @@ usage: valgrind [options] prog-and-args size/blocks, full: profile current and cumulative allocated size/blocks and freed size/blocks. --xtree-memory-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 '=') @@ -152,10 +156,6 @@ usage: valgrind [options] prog-and-args attempt to avoid expensive address-space-resync operations --max-threads= 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) diff --git a/none/tests/cmdline2.stdout.exp b/none/tests/cmdline2.stdout.exp index 241d33afa..28323ab06 100644 --- a/none/tests/cmdline2.stdout.exp +++ b/none/tests/cmdline2.stdout.exp @@ -79,6 +79,10 @@ usage: valgrind [options] prog-and-args size/blocks, full: profile current and cumulative allocated size/blocks and freed size/blocks. --xtree-memory-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 '=') @@ -154,10 +158,6 @@ usage: valgrind [options] prog-and-args attempt to avoid expensive address-space-resync operations --max-threads= 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) diff --git a/none/tests/cmdline2.stdout.exp-non-linux b/none/tests/cmdline2.stdout.exp-non-linux index 63af17bf7..0b6ad0cfa 100644 --- a/none/tests/cmdline2.stdout.exp-non-linux +++ b/none/tests/cmdline2.stdout.exp-non-linux @@ -77,6 +77,10 @@ usage: valgrind [options] prog-and-args size/blocks, full: profile current and cumulative allocated size/blocks and freed size/blocks. --xtree-memory-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 '=') @@ -152,10 +156,6 @@ usage: valgrind [options] prog-and-args attempt to avoid expensive address-space-resync operations --max-threads= 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)