Re: debugging GNAT programs

[kst@thomsoft.com (Keith Thompson)]

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'.