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,91c5b958fecf5eff,start
X-Google-Attributes: gid103376,public
From: Steve Gibson <gibson@ccis.adisys.com.au>
Subject: GNAT exception traceback
Date: 1997/06/11
Message-ID: <339EFAE3.26C@ccis.adisys.com.au>#1/1
X-Deja-AN: 247633889
Sender: usenet@ccis.adisys.com.au (usenet)
Organization: ADI Ltd.
Reply-To: gibson@ccis.adisys.com.au
Newsgroups: comp.lang.ada
Date: 1997-06-11T00:00:00+00:00
List-Id: <comp.lang.ada>


I have a question regarding exception tracing under the GNAT Ada95
compiler.

Running GNAT 3.05 on DOS 6.x and GNAT 3.07 on Solaris 2.5.1. On both
platforms, when an exception is raised and propagated to the top level
procedure ("main") and not caught, the code generated by the GNAT
compiler, correctly, reports "raised ADA.IO_EXCEPTIONS.DEVICE_ERROR" for
instance.
My question is, without running gdb or adding additional exception
handlers, is it possible to generate traceback information to determine
which line of code in which package generated the exception, and if so
how ?

For example:
    CONSTRAINT_ERROR exception raised in package XXX line i
    CONSTRAINT_ERROR exception propagated out of package YYY line j
    CONSTRAINT_ERROR exception propagated out of package Main line k

Thanks for any help.  

-- 
Steve Gibson
ADI Limited, CCIS Systems Group 
Email: gibson@ccis.adisys.com.au
Snail: 22 Stirling Hwy
       Nedlands
       Western Australia
Nbrs : (tel) +61 9 333 8917    (fax) +61 9 333 8889