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.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,cd24ffa36ebe3ef6,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-03-02 08:26:00 PST
Newsgroups: comp.lang.ada
Path: 
 bga.com!news.sprintlink.net!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!marc
From: marc@sei.cmu.edu (Marc Graham)
Subject: debugging GNAT programs
Message-ID: <1995Mar2.095243.14051@sei.cmu.edu>
Sender: netnews@sei.cmu.edu (Netnews)
Cc: gnat-request@cs.nyu.edu
Organization: The Software Engineering Institute
Date: Thu, 2 Mar 1995 09:52:43 EST
Date: 1995-03-02T09:52:43-05:00
List-Id: <comp.lang.ada>


To those of you using GNAT, do you have any hints about debugging?
Particularly "unhandled exceptions" (currently, GNAT just prints the
message: terminated due to unhandled exception (or something like
that) and, since it terminated, gdb can't find where the exception was
raised. (Anyway, gdb debugs the generated c code, not the Ada
code. Which makes it pretty useless.)

Of course, if the GNAT folk were to implement Ada.Exceptions, I could
solve this problem myself, (grumble, grumble, he hinted ... ;^} 

e-mail replies preferred. Thanks. 


Marc H. Graham                    Software Engineering Institute
marc@sei.cmu.edu                  Carnegie Mellon University
(412) 268 7784                    Pittsburgh, PA   15213