Re: c-stack: Catching stack overflow on most platforms without libsigsegv

Paul Eggert wrote: > That looks good, thanks. And thanks for all the work with libsigsegv. Pushed. Bruno

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

Hi Paul, > > (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