From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,7b1a523ee564a0f6
X-Google-Attributes: gid103376,public
From: dewar@schonberg.cs.nyu.edu (Robert Dewar)
Subject: Re: Where is exception Info?
Date: 1996/10/06
Message-ID: <dewar.844606089@schonberg>#1/1
X-Deja-AN: 187924360
references: <325160EB.254E@calvin.cca.rockwell.com>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-10-06T00:00:00+00:00
List-Id: <comp.lang.ada>


JR Crosmer asks

"In looking through the GNAT help for w95, I cannot even find the
word exception in the index.  Does this mean that the only way
to locate an unhandled exception is to use gdb?"

This is a system dependent question. We use standard sytem formats for
debugging information, so whether the information for a traceback is
available without using the debugger is system dependent. For example,
on VMS, a traceback is available, because the system is set up for this,
with special traceback information being a standard feature of object
files. In other systems, including Win95, the only way to get a traceback
is to use the debugging information via GDB. Of course GDB is completely
non-intrusive, so if you like you can easily setup to run all your programs
under GDB all the time, and it will not in anyway affect the behavior or
performance of these programs unless the breakpoint is hit.

If you don't find the information on how to do this by searching for the
word exception, you are not reading the GNAT documentation (gnatinfo.txt),
since this is described there!