Re: Texinfo 7.2.90 build with mingw.org's MinGW: testing

Gavin Smith <[email protected]>
Newsgroups gmane.comp.tex.texinfo.bugs
Message-ID <aWkgBwXNZh9mjDzq@orangestar>
On Thu, Jan 15, 2026 at 03:48:19PM +0200, Eli Zaretskii wrote:
> The second failure is strange: there's no *.diff files, but 2 of the 3
> files in res_parser are very different from out_parser.  The file
> out_parser/formatting.tex is empty, and out_parser/formatting.2 is
> missing 21 lines, and has this extra line:
> 
>   +Free to wrong pool 13beec0 not 88040400 at ../perl/Texinfo/Convert/LaTeX.pm line 2674.
> 
> This looks like some code used 'free' from a long 'malloc' to free
> some memory, like the allocation was done by Perl, but 'free' is from
> tta/C code, or vice versa.  How to investigate this?

Yes, you are probably right about the wrong 'free' being used.

The function called at that line in LaTeX.pm is index_element_sort_string
in tta/C/main/manipulate_indices.c.  But I don't know which "free" call
would be responsible under that function or why the Perl malloc would
have been used.

> And how do I know whether the tta/ tests were run with or without the
> XS extensions and the rest of C code in the tta/ directory?  (It might
> be a good idea to announce this when the test suite starts.)
> 
> All the other tests either succeeded or were skipped.

I think it's likely the XS modules were used in your test run.  I think
it's a good idea to report at the start of the output whether XS modules
are enabled.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.