With the latest incarnation, you can specify "no-abort" with either
--no-abort
on the command line, or
AUTOGEN_NO_ABORT=true
in the environment. The function "cleanup_and_abort()" handles
calls to abort() and those calls are now all guarded via:
diff --git a/agen5/autogen.c b/agen5/autogen
On Thu, Apr 6, 2017 at 8:56 AM, Andreas Schwab wrote:
> On Apr 05 2017, Bruce Korb wrote:
>
>> Yep. By design. It would fail and people asked me, "Why?" Without a
>> stack trace, there was no way to tell. I need to go back through and
>> not call abort when the failure is plainly obvious.
>
> Thi
On Apr 05 2017, Bruce Korb wrote:
> Yep. By design. It would fail and people asked me, "Why?" Without a
> stack trace, there was no way to tell. I need to go back through and
> not call abort when the failure is plainly obvious.
This may be the reason why the directives test leaves a process han
Yep. By design. It would fail and people asked me, "Why?" Without a
stack trace, there was no way to tell. I need to go back through and
not call abort when the failure is plainly obvious.
On Wed, Apr 5, 2017 at 1:50 AM, Andreas Schwab wrote:
> $ autogen --version
> autogen (GNU AutoGen) 5.18.12
