On Fri, 8 Dec 2017, Simon Sobisch wrote:
We use the autoconf generated testsuite script in GnuCOBOL to test the
compiler and runtime - and it works very well for "normal" tests.
There are some tests where the compiler should abort and it does, but
when it does so "correctly" by raising SIGABRT
Simon Sobisch writes:
> We use the autoconf generated testsuite script in GnuCOBOL to test the
> compiler and runtime - and it works very well for "normal" tests.
> There are some tests where the compiler should abort and it does, but
> when it does so "correctly" by
On 12/08/2017 02:36 PM, Simon Sobisch wrote:
> We use the autoconf generated testsuite script in GnuCOBOL to test the
> compiler and runtime - and it works very well for "normal" tests.
>
> There are some tests where the compiler should abort and it does, but
> when it does so "correctly" by
We use the autoconf generated testsuite script in GnuCOBOL to test the
compiler and runtime - and it works very well for "normal" tests.
There are some tests where the compiler should abort and it does, but
when it does so "correctly" by raising SIGABRT we can check for return
code 134 but get an