On Thu, Oct 08, 2026 at 09:51:31AM +0300, Eli Zaretskii wrote: > > This seems like a good hypothesis, probably MSYS2 uses nul and not NUL, > > so it does not match. I can fix that by making the comparison > > independent of the string case for nul. > > File-name comparison for the MinGW build of Texinfo should be > case-insensitive anyway, because the OS filesystem is.
As far as I can tell, it is not what we decided in the past, see https://lists.gnu.org/archive/html/bug-texinfo/2023-01/msg00038.html https://lists.gnu.org/archive/html/bug-texinfo/2023-01/msg00057.html The user should set explicitely -c CASE_INSENSITIVE_FILENAMES=1 Note that the comparison with "nul" is done independently of the file names comparison, so we can easily compare "nul" case insensitively, while still comparing file names in a case sensitive way. > Regarding your previous report of crashes in the test suite: > historically, most if not all such crashes I encountered were because > of mismatch between allocation of memory and freeing it: either > allocation via Perl and freeing via a direct call to 'free', or the > other way around, allocation via 'malloc' with subsequent freeing via > Perl. They use different 'malloc'/'free' implementations that use > different memory pools, so this usually causes aborts and crashes. So > maybe look into such possibilities in the code involved in crashing. That could be that, but the tests with texi2any.pl with C/XS do not crash, only the tests with ctexi2any, so it could also be something else in the main program. Also, for this release, there has not been that much change in the HTML code where those issues are more likely, the new plaintext and Info in C have much less back and forth from Perl/C. Let's see if we can get a backtrace. -- Pat
