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.2 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cb928f3522d58650
X-Google-Attributes: gid103376,public
From: Stephen Leake <Stephen.Leake@gsfc.nasa.gov>
Subject: Re: Two GNAT questions
Date: 1997/11/14
Message-ID: <346C861A.7299@gsfc.nasa.gov>#1/1
X-Deja-AN: 290071617
References: <64fska$a8q$1@ultranews.duc.auburn.edu>
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Reply-To: Stephen.Leake@gsfc.nasa.gov
Newsgroups: comp.lang.ada
Date: 1997-11-14T00:00:00+00:00
List-Id: <comp.lang.ada>


John M. Greer wrote:
> 
> Question 1:  Exception traceback
> 
> I think somewhere I saw an example of how GNAT was able to trace
> exceptions back and report the line in which they were raised.  I looked
> in the online manual and everywhere else I could think of, but was unable
> to find that feature.  Could someone point me in the right direction?

run your executable under gdb (the gnu debugger), set a break on
'__gnat_raise'. then use the gdb 'where' command. See the gnat user
guide topic "using gdb".

> Question 2:  Is there any way to find/display the parameters of your
> current GNAT installation?  Basically, I need to find every directory
> GNAT accesses on my machine (Linux ELF).  (In case you're wondering, I
> want to compile via NFS, where the NFS'd machine is not sharing my path,
> and my root is not his root.  Yeah, it's a lot of trouble, but he's out
> of hard drive space.  :-)

You can try running gnatmake with "-v" and "-gnatv"; see the gnat user
guide for more switches that output useful information.

> 
> John Greer
> greerjo@mail.auburn.edu

-- 
- Stephe