From: Kevin Rigotti DRA <rigotti@atc.dra.hmg.gb>
Subject: Re: [Gnat] Finding exceptions without gdb
Date: 1996/11/07
Date: 1996-11-07T00:00:00+00:00 [thread overview]
Message-ID: <3281A927.48ED@atc.dra.hmg.gb> (raw)
In-Reply-To: 32809C5B.6057@gsfc.nasa.gov
Stephen Leake wrote:
> Exceptions can be caught by breaking in the "__gnat_raise" routine and
> then doing a "bt" or "where" command.
If your code uses exceptions for non-fatal "error" handling, such
as 'file not found' when opening log files, then __gnat_raise gets
called rather too often to be useful.
If the exception is one you define yourself then it is worth wrapping
it in a procedure call. That way you can set a breakpoint on the
wrapper and get a stack back-trace, plus whatever diagnostics you
choose to put in the wrapper.
Just my $0.02
Kevin
prev parent reply other threads:[~1996-11-07 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-04 0:00 [Gnat] Finding exceptions without gdb Bob Collins
1996-11-05 0:00 ` Robert Dewar
1996-11-06 0:00 ` Stephen Leake
1996-11-06 0:00 ` Stephen Leake
1996-11-07 0:00 ` Kevin Rigotti DRA [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox