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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID,
	RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,91c5b958fecf5eff
X-Google-Attributes: gid103376,public
From: "wiljan" <W.Derks@nl.cis.philips.com>
Subject: Re: GNAT exception traceback
Date: 1997/06/16
Message-ID: <01bc7a82$c57186a0$2a208b82@wd>#1/1
X-Deja-AN: 248875474
References: <199706131810.OAA07239@seahunt.ctron.com> <dewar.866242346@merv>
Organization: Philips Electronics N.V.
Newsgroups: comp.lang.ada
Date: 1997-06-16T00:00:00+00:00
List-Id: <comp.lang.ada>




Robert Dewar <dewar@merv.cs.nyu.edu> wrote in article
<dewar.866242346@merv>...
> Huy says
> 
> << 
> I'd think dumping a core would be nice; at least you can look at the call
> stack. But doing it the C way would be sacrilegious, right?
>  >>
> 
> No, that's the point, you can't look at the call stack in a core dump,
because
> by the time you know an exception is unhandled, it's too late, the stack
has
> been unwound and destroyed. This is something that needs improving in
future
> versions of GNAT (the SGI version of GNAT using WORKSHOP handles this
nicely
> right now).
Note that this will only allow to get to the exception raised by the main
program.
When exceptions happen in tasks they simply disappear without a message
or anything from the program (at least on NT).
I myself made a small patch to a-raise.c so that it will generate a
traceback
whenever a constraint error is raised. This patch only works on ix86
machines.
Anyway for me it is a big release because it allows me to locate 99% of the
constraint errors.
I use gdb to calculate the exact location of the pc that are reported in
hex in the
traceback.

Wiljan