branch master updated: * README-hacking: advice on 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 6b038d9433 * README-hacking: advice on valgrind
6b038d9433 is described below

commit 6b038d94339d6de4ef38bbc61877c586a48f77a8
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Tue Oct 25 15:12:20 2022 +0100

    * README-hacking: advice on valgrind
---
 ChangeLog      | 4 ++++
 README-hacking | 5 ++++-
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index f856a80d7e..dec35790f8 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2022-10-25  Gavin Smith  <gavinsmith0123@gmail.com>
+
+       * README-hacking: advice on valgrind
+
 2022-10-25  Gavin Smith  <gavinsmith0123@gmail.com>
 
        * doc/texinfo.texi (@minus): Do not state that '-' produces
diff --git a/README-hacking b/README-hacking
index 6bee8dde28..466ed8a1a3 100644
--- a/README-hacking
+++ b/README-hacking
@@ -208,7 +208,10 @@ files in build-aux and elsewhere.  Check changes before 
committing.
 
 Use util/srclist-txi for checking files to be copied from gnulib
 
-run all tests with valgrind
+run all tests with valgrind:
+* under info/t, put valgrind in $ginfo, then check t/*.val.log files after
+  running test suite
+
 parsetexi memory leak checks with valgrind
 
 NYTProf profiling for Perl code to check for avoidable hotspots