patgen SIGSEGV on aarch64-linux

[Johannes Hielscher]

Hi,

the test suite disclosed a newly emerged issue on trunk/tl2020-dev: the
patgen binary instantly segfaults on aarch64-linux.


Built with "-O0 -g", I got:

$ gdb ./patgen
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
[…]
Reading symbols from ./patgen...done.
(gdb) r
Starting
program: /opt/texlive/svn_trunk/trunk/Build/source/Work-dist-aarch64-linux/texk/web2c/patgen
During startup program terminated with signal SIGSEGV, Segmentation
fault.

$ strace ./patgen
execve("./patgen", ["./patgen"], [/* 39 vars */]) = -1 ENOMEM (Cannot
allocate memory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL,
si_addr=NULL} --- +++ killed by SIGSEGV +++
Segmentation fault


No changes in ulimit, same platform, compiler, et al. since successful
TL2019 final builds, and the same happens on my other aarch64-linux
system. On, x86_64-linux the binary built from the same sources does run
unsuspiciously.

I suspect that the changes of trie{,c}_size with -r51154 and/or -r51201
(from mid-may, following Keno's request, see thread
<https://tug.org/pipermail/tex-live/2019-May/043672.html>) had weird
side effects on some platforms. Any ideas?


Best,
Johannes