branch master updated: * README-hacking: use suppressions file for valgrind

[Gavin D. Smith]

This is an automated email from the git hooks/post-receive script.

gavin pushed a commit to branch master
in repository texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new be72774942 * README-hacking: use suppressions file for valgrind
be72774942 is described below

commit be72774942e1875ec2318814f89e82370004a716
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Sat Apr 13 21:20:18 2024 +0100

    * README-hacking: use suppressions file for valgrind
---
 ChangeLog      | 4 ++++
 README-hacking | 7 +++++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 64fd654361..9b19db4a95 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2024-04-13  Gavin Smith <gavinsmith0123@gmail.com>
+
+       * README-hacking: use suppressions file for valgrind
+
 2024-04-13  Patrice Dumas  <pertusus@free.fr>
 
        * tp/Texinfo/ManipulateTree.pm, tp/Texinfo/Common.pm,
diff --git a/README-hacking b/README-hacking
index 1299d70c4c..0eb419f65a 100644
--- a/README-hacking
+++ b/README-hacking
@@ -259,13 +259,16 @@ run all tests with valgrind:
   Add line "use Perl::Destruct::Level level => 1;" to texi2any.pl
   when running 'valgrind --leak-check=full' to make perl clean it
   its allocations.  Run e.g.
-      valgrind --log-file=val.log --leak-check=full \
+      valgrind --suppressions=texi2any.supp --log-file=val.log \
+               --leak-check=full \
         perl ../tp/texi2any.pl ../doc/info-stnd.texi
   and other input files.
 
   Add line "use Perl::Destruct::Level level => 1;" to t/test_utils.pl
   Check tests with e.g.
-    for f in t/*.t ; do valgrind --log-file=val.log-${f#t/} --leak-check=full \
+    for f in t/*.t ; do valgrind --suppressions=texi2any.supp \
+                                 --log-file=val.log-${f#t/} \
+                                 --leak-check=full \
           perl -w $f ; done
  (could take 1-2 hours to finish).  check log files one by one afterwards.