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
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 1995-03-06 00:13:50 PST
Path: 
 bga.com!news.sprintlink.net!hookup!news.mathworks.com!news.duke.edu!convex!bcm!newsfeed.rice.edu!hsdndev!yale!not-for-mail
From: griest-tom@cs.yale.edu (Tom Griest)
Newsgroups: comp.lang.ada
Subject: Re: debugging GNAT programs
Date: 3 Mar 1995 23:26:20 -0500
Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158
Message-ID: <3j8q5cINNsdr@RA.DEPT.CS.YALE.EDU>
References: <D4to84.FJr@world.std.com> <3j5vvu$6c2@newsbf02.news.aol.com>
NNTP-Posting-Host: dept-gw.cs.yale.edu
Date: 1995-03-03T23:26:20-05:00
List-Id: <comp.lang.ada>

In article <3j5vvu$6c2@newsbf02.news.aol.com> pug156@aol.com (Pug 156) writes:
>I think the release notes or maybe gnatinfo.txt says something about
>setting a break point on the run time's raise_exception routine.  See the
>notes for the actual name.  Try gnatinfo.txt first, I think its there.


__gnat_raise is only called for unhandled exceptions (which was
the original question).  If you want to catch any exception you 
have to also set a breakpoint on the longjmp routine.  
(I'm not sure that this isn't used for things other than just 
exception propogation, but it seems to work reliably.)

-Tom