Re: debugging GNAT programs

[vladimir@speedy.intrepid.com (Vladimir Vukicevic)]

In article <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.

The exception raising routine is called __gnat_raise. Set a breakpoint
there to catch exceptions.

> (Anyway, gdb debugs the generated c code, not the Ada code. Which
> makes it pretty useless.)

The main Ada procedure is called _ada_(procedure_name). If your 'main'
procedure is called FOO, then set a break on _ada_foo to begin debugging
on entry to your program.

Another thing to know is that if you want to step into a dispatching call,
you have to step through some internal gnat procedures which find the address
of the real function in the vtable.

	-- Vladimir Vukicevic
	-- vladimir@intrepid.com