On Sun, Sep 24, 2017 at 08:53:46PM +0300, Shlomi Fish wrote:
> I see. Well, the general wisdom is that a program should not ever segfault,
> but
> instead gracefully handle the error and exit.
This only applies to applications, not to tools that let YOU write
applications.
I can write a trivial
I'm forwarding this bug report by Robert Nagy ,
which also concerns bash 4.4:
>
Unbreak autoconf checks with clang by not using nested functions
in the checks.
Someone clearly did not read the autoconf documentation because
using the following functions with a function declaration
On 9/25/17 1:14 PM, Christian Weisgerber wrote:
> I'm forwarding this bug report by Robert Nagy ,
> which also concerns bash 4.4:
>
> >
> Unbreak autoconf checks with clang by not using nested functions
> in the checks.
Thanks for the report. This has clearly not been too serious
On 09/24/2017 12:53 PM, Shlomi Fish wrote:
>
> I see. Well, the general wisdom is that a program should not ever segfault,
> but
> instead gracefully handle the error and exit.
This is possible by installing a SIGSEGV handler that is able to
gracefully exit the program when stack overflow is de
