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: #1/1 X-Deja-AN: 249143858 References: <339EFAE3.26C@ccis.adisys.com.au> <33A22F37.41CBA26B@erols.com> <33A5A600.298A@no.such.com> Organization: New York University Newsgroups: comp.lang.ada Date: 1997-06-17T00:00:00+00:00 List-Id: Wes says <> Feel free to jam away :-) Seriously, this is a very big project, for all sorts of reasons. Wes, if you do dig into it, you will quickly discover why. Basically the devil is in the details as usual, but in this case, the details are very considerable. Here is a little one: you need to have access to the debugging information from within the program if you use this approach, and indeed you will need large amounts of space to read in this debugging information (we hope that the traceback you are trying give is not for Storage_Error). But getting your hands on this information is not easy. But that's just for starters. Whenever you have trouble with someone saying that X is a lot of work, and you know nothing much about X, then probably the first step in verifying the reasonableness of your trouble is to learn about X. So my invitation is as follows: dig away in the GDB code, and if you see a way of doing this as simply as you feel should be possible, by all means suggest it! Robert