Re: GNAT exception traceback

["wiljan" <W.Derks@nl.cis.philips.com>]

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