develooper Front page | perl.perl5.porters | Postings from November 2022

Re: perl-5.37.5 breaks texinfo-7.0

Thread Previous | Thread Next
From:
Dave Mitchell
Date:
November 13, 2022 15:12
Subject:
Re: perl-5.37.5 breaks texinfo-7.0
Message ID:
Y3EJRvZTBRslvu/k@iabyn.com
On Sun, Nov 13, 2022 at 02:22:28AM +0100, Uwe Düffert wrote:
> 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

It's very unclear what problem you are describing.

Are saying

1) that texinfo-7.0 won't install with a normal perl-5.37.5 build?
In which case what is the error? Is the valgrind log just provided as
something that might help us identify the problem?

Or that

2) that texinfo-7.0 happily installs and/or runs with a normal perl-5.37.5
build, but running part of the process (install? runtime?) under valgrind
shows an issue that may need investigating?

Or....?

Note that building a perl with debugging symbols means the valgrind output
displays line numbers as well as function names, which makes
understanding the output easier.

A quick look at the valgrind output shows that some texinfo XS code calls
Perl_switch_to_global_locale(), which mallocs() a block (via duping a
string with savepv) then directly frees it (probably within the same
call to Perl_switch_to_global_locale()). Then later, that same block is
freed again in a leave_scope() call.

Without line numbers its difficult to comment further. Also, on my build,
nothing in Perl_switch_to_global_locale() calls free() directly.

-- 
Monto Blanco... scorchio!

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About