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,91c5b958fecf5eff
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: GNAT exception traceback
Date: 1997/06/17
Message-ID: <dewar.866578001@merv>#1/1
X-Deja-AN: 249143868
References: <339EFAE3.26C@ccis.adisys.com.au> <dewar.866126413@merv>
 <33A22F37.41CBA26B@erols.com> <dewar.866289217@merv>
 <33A5A734.76D9@no.such.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-06-17T00:00:00+00:00
List-Id: <comp.lang.ada>


<<How much would it improve the above "problem" to store the traceback
as a list of addresses, and only convert into human-readable form
when Exception_Information is called?  Not too long ago, someone
helped me do something similar with Alsys, and most of the stack
traces were less than a dozen addresses.>>

Notice that this would be pretty easy once you have the new exception
implementation, since that has to be able to unwind the stack in any case,
so it already faces this tough problem (which is why this improved
exception implementation has not appeared yet!)