Re: m4-1.4.19.60-6ebfc: some core dumps

Hi Claus and Eric,

> > System information (uname -a): OpenBSD 7.0 GENERIC#2
> > 
> > .. contents:: :depth: 2
> > 
> > FAIL: test-c32isblank.sh
> > ========================
> > 
> > test-c32isblank.c:109: assertion 'is == 0' failed
> > Abort trap (core dumped) 
> > FAIL test-c32isblank.sh (exit status: 1)
> > 
> > FAIL: test-c32isgraph.sh
> > ========================
> > 
> > test-c32isgraph.c:161: assertion 'is != 0' failed
> > Abort trap (core dumped) 
> > FAIL test-c32isgraph.sh (exit status: 1)
> 
> Bruno will probably be able to fix this in gnulib, and I'll be sure to
> pick up a newer version of gnulib before cutting 1.4.20.

These failures don't occur in OpenBSD 7.5 and 7.6.

If OpenBSD 7.0 was still maintained, I would fix these test failures in
gnulib. But the support policy of OpenBSD is that only the last 2 releases
are supported, and since they have a release frequency of 2 / year,
OpenBSD 7.0 is end-of-life already for 2.5 years (since Oct 2022). See
https://en.wikipedia.org/wiki/OpenBSD#Releases .

> > ------------------------------------------------------------
> > Note: there is also a third core file: test-c-stack.core
> 
> Hmm - so you're stating that running the testsuite created a core file
> but passed?  That's worth some investigation as well.  Do you have
> libsigsegv installed on the platform, or not, as that may impact how
> gnulib's test-c-stack behaves.

I reproduce this core dump as well. But that's OK: The test-c-stack.sh
test merely verifies that before m4 exits, it prints "stack overflow".

Bruno