On Sun, 13 Nov 2022 at 02:22, Uwe Düffert <dueffert@uwe-dueffert.de> wrote: > > Dear Karl / perl5-porters, > > remember July? I did have a problem with perl-5.37.1 and perl-5.37.2 not > being able to compile texinfo-6.8 and it took quite a few iterations to > get that fixed... > > Well, TROUBLE IS BACK! > > While with perl-5.37.4 it was still possible to build texinfo-7.0, that > fails with perl-5.37.5 - in a very similar way as in July: > > The perl command from texinfo-7.0 doc build as in > https://uwe-dueffert.de/code/perl5.37.5/texinfo-7.0_doc_problem.sh > has memory access issues again: > https://uwe-dueffert.de/code/perl5.37.5/texinfo-7.0_valgrind.log > > Let me know if I shall try or provide anything, e.g. in case you have > trouble reproducing that. When you run valgrind and things like that you should set PERL_DESTRUCT_LEVEL. B<NOTE 2>: To minimize the number of memory leak false alarms (see L</PERL_DESTRUCT_LEVEL> for more information), you have to set the environment variable PERL_DESTRUCT_LEVEL to 2. For example, like this: env PERL_DESTRUCT_LEVEL=2 valgrind ./perl -Ilib ... Looking at your valgrind output it looks to me like you ran it with a normal destruct level, so it deliberately does not bother freeing certain data structures at tear down. Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"Thread Previous | Thread Next