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,fbd3a4df7893995d
X-Google-Attributes: gid103376,public
From: Gautier <Gautier.deMontmollin@Maths.UniNe.CH>
Subject: Re: GNAT/Ada Traceback Information?
Date: 1999/06/07
Message-ID: <375B9E98.D81FF99B@Maths.UniNe.CH>#1/1
X-Deja-AN: 486606989
Content-Transfer-Encoding: 7bit
References: <375AB243.F2176DA5@voyager.net>
To: Henry Rosenbrock <rosenbr@voyager.net>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-06-07T00:00:00+00:00
List-Id: <comp.lang.ada>

> I was looking for an Ada standard way of recording the traceback
> information for exceptions. With our current Ada83 compiler(VADS) we had
> to write assembly code to manually trace back the stack within the
> exception handlers. When I started to investigate GNAT and Ada95, I
> noticed that the information was said to be stored in the
> Ada.Exceptions.Exception_Occurence. The type was private, but that can
> be easily fixed. The problem is that no traceback information is ever
> stored into the structure. Does anybody know if this structure was
> created for future enhancements or if it us only active for certain
> targets? Our final target is a PowerPC, but I am current doing the
> research on a Linux i686 box.

A possibility is to adapt the AD trace-back tool that works
on GNAT/DOS & GNAT/NT.
Bin+Sources @ http://members.xoom.com/gdemont/logiciel/ad.zip
Web page http://members.xoom.com/gdemont/ad.htm

Good luck!

-- 
Gautier

http://members.xoom.com/gdemont/