From: Bruno Haible Date: Wed, 23 Jul 2025 07:32:25 +0000 (+0200) Subject: run-test: Suggest a more reliable way of invoking valgrind. X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=516d94893d53e9d19d68254715dcad20bc12aea6;p=thirdparty%2Fgnulib.git run-test: Suggest a more reliable way of invoking valgrind. * build-aux/run-test (func_usage): Suggest to use the --error-exitcode option. --- diff --git a/ChangeLog b/ChangeLog index 8a226b449a..0bca5616a4 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2025-07-23 Bruno Haible + + run-test: Suggest a more reliable way of invoking valgrind. + * build-aux/run-test (func_usage): Suggest to use the --error-exitcode + option. + 2025-07-23 Bruno Haible thrd: Avoid conversion between different function pointer types. diff --git a/build-aux/run-test b/build-aux/run-test index de8678dc3c..53167320c3 100755 --- a/build-aux/run-test +++ b/build-aux/run-test @@ -31,6 +31,8 @@ Usage: run-test [OPTION...] CHECKER PROGRAM [ARGUMENT...] Runs PROGRAM under the control of CHECKER. CHECKER may be empty or a valgrind command with some options, such as +'valgrind --tool=memcheck --error-exitcode=9 --num-callers=20' +or 'valgrind --tool=memcheck --num-callers=20 --leak-check=yes --leak-resolution=high --show-reachable=yes'. When CHECKER is not empty, it is recommended that the package has been