Re: Ada and C++ asserts.

[richard@curnow.demon.co.uk (Richard Curnow)]

In article <31EE4C88.1AAD@ubs.com> Ian Johnston <ian.johnston@ubs.com> writes:

    Ian> On any UNIX, you can look at the core dump with a debugger
    Ian> and get a stack trace showing not only where the core dump
    Ian> happened, but the chain of function calls leading up to it,
    Ian> along with parameter and variable values. Even on VMS, you
    Ian> get a stack trace showing how you arrived at the assert.

    Ian> What information does Ada supply about the circumstances
    Ian> leading to the failed assertion?

With GNAT, the normal behaviour is to stop execution of the program
with a "raised SYSTEM.ASSERTIONS.ASSERT_FAILURE" message.  However,
during development, the program can be compiled with "-g" and then run
under a breakpoint debugger such as gdb.  If a breakpoint is set on
"system__assertions__raise_assert_failure" a stack trace can be
produced whenever an exception is raised due to an assertion being
failed.  A little unwieldy compared to a post-mortem gdb session on a
C or C++ -generated core file, but effective nevertheless.

Cheers
Richard
-- 
Richard P. Curnow
Stevenage, England