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,c1d47f740d49a6c6
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: GDB with GNAT
Date: 1996/04/16
Message-ID: <dewar.829687408@schonberg>#1/1
X-Deja-AN: 147910304
references: <4l0og5$4e8@arl-news-svc-2.compuserve.com>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-04-16T00:00:00+00:00
List-Id: <comp.lang.ada>

Rob asks

"Does anyone know how to make the debugger stop as soon
as an exception is raised in gdb with gnat.
With another compiler I can do
break exc_dispatch_exception allowing you to do a
'where' before the exception is propagated (and possibly
handled)

Any help would be much appreciated,"

This information is in the documentation (gnatinfo.txt). If you do not
have a copy of this file, your first job should be to track it down. It
is included in every distributino of GNAT, and has a section on the
debugger that answers this and other questions about GDB!