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-05 05:16:39 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!hookup!newshost.marcam.com!uunet!telesoft!kst From: kst@thomsoft.com (Keith Thompson) Subject: Re: debugging GNAT programs Message-ID: Originator: kst@pulsar Sender: news@thomsoft.com (USENET News Admin @flash) Organization: Thomson Software Products, San Diego, CA, USA References: <1995Mar2.095243.14051@sei.cmu.edu> Date: Thu, 2 Mar 1995 22:23:52 GMT Date: 1995-03-02T22:23:52+00:00 List-Id: In <1995Mar2.095243.14051@sei.cmu.edu> marc@sei.cmu.edu (Marc Graham) writes: > 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.) First of all, there is no generated C code. The name GNAT (GNU Ada Translator) is perhaps slightly misleading, but it's a true compiler that happens to share a backend with several other GNU compilers. I found this in "using GDB" gnatinfo.txt, which is part of the GNAT distribution: > Exceptions can be caught by breaking in the "__gnat_raise" routine and then > doing a "bt" or "where" command. (Speaking for nobody as always.) -- Keith Thompson (The_Other_Keith) kst@thomsoft.com (kst@alsys.com still works) TeleSoft^H^H^H^H^H^H^H^H Alsys^H^H^H^H^H Thomson Software Products 10251 Vista Sorrento Parkway, Suite 300, San Diego, CA, USA, 92121-2718 That's Keith Thompson *with* a 'p', Thomson Software Products *without* a 'p'.