Re: sigsegv, c-stack: Avoid compilation error with glibc >= 2.34

[Paul Eggert]

On 5/16/21 7:33 PM, Bruno Haible wrote:
> I don't have time to rewrite all these unit tests and autoconf tests.

Can we assume you wouldn't mind if someone did take the time? (Not that 
I'm volunteering right just now.)


> (Additionally, if we were to use malloc() as a replacement, watch out
> that malloc()ed memory may not be executable, but some programs need
> an executable stack.)

That shouldn't be a problem on GNU platforms, since it's documented that 
you can malloc the alternate signal stack. If it does turn into a 
problem, I suppose we can assume that when SIGSTKSZ is not a constant 
that malloc should work (otherwise how could you ever create an 
alternate signal stack?).