From: Steve Quinlan <steven.quinlan@nospam.lmco.com>
Subject: Re: A small Ada success story
Date: 1999/03/26
Date: 1999-03-26T00:00:00+00:00 [thread overview]
Message-ID: <36FBBE31.348E17A4@nospam.lmco.com> (raw)
In-Reply-To: 7cth1u$9vb@top.mitre.org
> T.E.D.> I sure wish more compiler vendors made this
> > information (line number of an exception occurrence)
> > available without using a debugger.
>
> I agree, this would be a welcome enhancement.
This is becoming more common. OC Systems compiler has had this for years.
Not only does an unhandled exception give a symbolic traceback to stdout, but
there are interfaces to get this information in the runtime as well, so that
a program which has an exception can record (through some error reporting
service) the information about that exception needed to debug it. In domains
where your app. is running in an environment where there is no user sitting
at a terminal to see and record the screen dump, this has been very important
to use in being able to debug problems. We have an entire Error
Reporting/Recording architecture built around the ability of programs to
detect error conditions, pass data to the Error Reporting Service, and get
the data as well as symbolic tracebacks recorded for later offline analysis.
I did a compiler trade study last year to select an Ada compiler for a new
FAA Air Traffic Control project, and one criteria was that the compiler
either have or be willing to develop support for getting symbolic exception
tracebacks with line numbers at runtime. In addition, we want to be able to
get symbolic stackbacks from any arbitrary point in the code (not necessarily
in an exception scope). Aonix was already adding the exception support.
Rational was as well, but only wanted to provided non-symbolic PC values
which would have to be run through a tool to get symbolics. GNAT developed
such a feature for us.
Of course, it is true that there is no standard across vendors, but I don't
see that as too much of a problem. We've managed to encapsulate these things
in the Error Reporting service. Whether we use OCS or GNAT specific
interfaces is hidden from the application programs that detect and record
their own errors.
Steve Quinlan
prev parent reply other threads:[~1999-03-26 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-14 0:00 A small Ada success story Steffen Huber
1999-03-17 0:00 ` Nick Roberts
1999-03-17 0:00 ` Tom Moran
1999-03-17 0:00 ` dennison
1999-03-18 0:00 ` Corey Ashford
1999-03-18 0:00 ` bill
1999-03-19 0:00 ` Fraser Wilson
1999-03-21 0:00 ` Ehud Lamm
1999-03-21 0:00 ` robert_dewar
1999-03-21 0:00 ` Tom Moran
1999-03-21 0:00 ` robert_dewar
1999-03-22 0:00 ` Simon Wright
1999-03-19 0:00 ` Larry Kilgallen
1999-03-20 0:00 ` locating exceptions (Ada vs. Java) Markus Kuhn
1999-03-20 0:00 ` bill
1999-03-19 0:00 ` A small Ada success story dewar
1999-03-18 0:00 ` locating exceptions (was: Ada success story) Markus Kuhn
1999-03-19 0:00 ` A small Ada success story Michael F Brenner
1999-03-26 0:00 ` Steve Quinlan [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