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=0.6 required=5.0 tests=BAYES_40,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,fbd3a4df7893995d,start
X-Google-Attributes: gid103376,public
From: Henry Rosenbrock <rosenbr@voyager.net>
Subject: GNAT/Ada Traceback Information?
Date: 1999/06/06
Message-ID: <375AB243.F2176DA5@voyager.net>#1/1
X-Deja-AN: 486372233
Content-Transfer-Encoding: 7bit
X-AUTHid: rosenbr4
Organization: Michigan State University
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-06-06T00: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.

Henry Rosenbrock Jr.
Senior Software Engineer
Smiths Industries Aerospace
3290 Patterson Ave, S.E.
Grand Rapids MI, 49512