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 8a226b449a9ab3f3aafc83213ffb17488ace27f5..0bca5616a4b4c59f2559b4ce2e835cf664526494 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2025-07-23  Bruno Haible  <bruno@clisp.org>
+
+       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  <bruno@clisp.org>
 
        thrd: Avoid conversion between different function pointer types.

diff --git a/build-aux/run-test b/build-aux/run-test
index de8678dc3ce494ecf9efacb327a378226f3cd1da..53167320c35fc5d729a94beaac7bb9cface6e98d 100755 (executable)
--- 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