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,2c0bee8a07770dd4 X-Google-Attributes: gid103376,public From: Stephen Leake Subject: Re: [Gnat] Finding exceptions without gdb Date: 1996/11/06 Message-ID: <32809C5B.6057@gsfc.nasa.gov>#1/1 X-Deja-AN: 194871688 references: content-type: text/plain; charset=us-ascii organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA mime-version: 1.0 reply-to: Stephen.Leake@gsfc.nasa.gov newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (Win95; U) Date: 1996-11-06T00:00:00+00:00 List-Id: As has been pointed out many times, there is full documentation on how to use gnat, including how to use gdb with gnat compiled code, in the gnat documentation, specifically the file doc/gnatinfo.txt. Yes, this is a flat text file; that's what "search" commands in text editors are for! Searching for "gdb" and then "exceptions", we find: Exceptions can be caught by breaking in the "__gnat_raise" routine and then doing a "bt" or "where" command. Happy debugging! -- - Stephe