On Sun, Oct 13, 2024 at 03:30:14PM +0100, Gavin Smith wrote: > We have had memory errors with setenv in XS code before.
Might indeed be related, though the issues were much less severe who knows what could happen on other platforms. > I wrote on November 16, 2023 (private mail): > > > I found this entry in "man perldelta" for 5.38.0: > > > > • Perl is no longer manipulating the "environ" array directly. The > > variable "PL_use_safe_putenv" has been removed and > > "PERL_USE_SAFE_PUTENV" is always defined. This means XS modules > > can > > now call "setenv" and "putenv" without causing segfaults. [perl > > #19399 <https://github.com/Perl/perl5/issues/19399>] > > > > I don't know the perl internals enought to say whether this is exactly the > > same problem that we were facing, but it seems to be fixed, anyway. Linked > > reports seemed similar to the problem we had. > > This was in relation to many errors being logged by valgrind. > > Do you know what version of Perl is in use? Seems to be perl5: 5.36.3_2 > Does this report relate to https://github.com/gnu-texinfo/ci-check? Yes. > Do you have a more specific link about where to get the build reports? https://github.com/gnu-texinfo/ci-check/actions/runs/11289616593/job/31400276091 -- Pat
