[no subject]

[Gavin D. Smith]

branch: master
commit 490d66bfd7185cf5dd1a17f70d0c8b8aa497e0d5
Author: Gavin Smith <gavinsmith0123@gmail.com>
AuthorDate: Thu Dec 19 19:44:34 2024 +0000

    * README-hacking: mention CFLAGS='-g -O0' to prevent false
    positives for valgrind.
---
 ChangeLog      | 5 +++++
 README-hacking | 7 +++++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index c90fff4a7a..c5719c2179 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2024-12-19  Gavin Smith <gavinsmith0123@gmail.com>
+
+       * README-hacking: mention CFLAGS='-g -O0' to prevent false
+       positives for valgrind.
+
 2024-12-19  Gavin Smith <gavinsmith0123@gmail.com>
 
        * install-info/tests/defs.in: adjust valgrind invocation to
diff --git a/README-hacking b/README-hacking
index 00011095e1..d611dbed36 100644
--- a/README-hacking
+++ b/README-hacking
@@ -307,9 +307,12 @@ callgrind profiling for XS code
 
 run all tests with valgrind:
 * in info/t/Init-test.inc, put valgrind in $ginfo, then check t/*.val.log
-  files after running test suite
+  files after running test suite.  Note that some tests may report leaks
+  unless info is compiled with CFLAGS='-g -O0'.
 * edit install-info/tests/defs.in, uncomment valgrind line and run
-  config.status to regenerate defs
+  config.status to regenerate defs.  Note that some tests may report leaks
+  unless install-info is compiled with CFLAGS='-g -O0'.
+
 * XS modules memory leak check checking with valgrind
   Add line "use Perl::Destruct::Level level => 1;" to texi2any.pl
   when running 'valgrind --leak-check=full' to make perl clean it