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 Subject: Re: Two GNAT questions Date: 1997/11/18 Message-ID: <3471A89A.78F5@gsfc.nasa.gov>#1/1 X-Deja-AN: 290529081 References: <64fska$a8q$1@ultranews.duc.auburn.edu> <346C861A.7299@gsfc.nasa.gov> Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA Reply-To: Stephen.Leake@gsfc.nasa.gov Newsgroups: comp.lang.ada Date: 1997-11-18T00:00:00+00:00 List-Id: Robert Dewar wrote: > > Stephen Leake said > > < '__gnat_raise'. then use the gdb 'where' command. See the gnat user > guide topic "using gdb". > >> > > That is correct advice for older obsolete versions of GDB, but with the > current Ada mode version of GDB, there is a command > > break exception [exception name] > > command that can be used to achieve this effect more directly Sorry, Robert, but since this question was posted on the newsgroup, I assumed he was refering to the publicly available GNAT 3.10. That user's guide makes no mention of "break exception", and on Windows, there is no Ada aware gdb. The original poster did not mention what OS he was on, so I assumed the most common (or at least the one I use :). There is nothing "obsolete" about this version of gdb, since it is the only one available for this platform! -- - Stephe