Re: stack smashing detected

[Finn Thain <fthain@linux-m68k.org>]

On Sat, 18 Feb 2023, Andreas Schwab wrote:

> On Feb 18 2023, Finn Thain wrote:
> 
> > Why do you say init ignores SIGABRT?
> 
> PID 1 is special, it never receives signals it doesn't handle.
> 

I see. I wonder if there is some way to configure the kernel so that PID 1 
could be aborted for fstack-protector. I doubt it.

My gut says that a compiler change somehow made the fstack-protector 
implementation insensitive to kernel configuration.

So I still think that, if Stan adopted Debian's build environment, random 
processes would cease to be aborted (regardless of kernel .config).