Re: Alternative for Gnat Studio

[ldries46 <bertus.dries@planet.nl>]

Op 2-3-2021 om 6:11 schreef John Perry:
> On Sunday, February 28, 2021 at 4:54:30 PM UTC-6, Stephen Leake wrote:
>> "Dmitry A. Kazakov" <mai...@dmitry-kazakov.de> writes:
>>
>>> GDB and IDE are different things. GDB never really worked for complex
>>> projects and, I am afraid, it never will.
>> GDB has always met my needs, programming spacecraft simulators for NASA.
>>
> Honest question: do you have advice for debugging exceptions in GDB?*** I had to debug an exception the other day & I had a humdinger of a time determining what caused it. When the Ada RT raises an exception in GDB, GDB quits the program state altogether, so I have to employ guess-and-check methods to figure out where, say, an Ordered_Map Key_Error occurs. This is contrary to how GDB handles C++ exceptions: the program stops immediately, so that you can examine the state, move up and down through the stack, etc.
>
> I've used GDB a lot with C++, so I don't find it as bad as Dmitry says, but it's a much poorer experience when debugging Ada. (Still useful!)
>
> ***Aside from writing programs that don't raise them, of course. ;-)
I am normally using severaldifferent methods of debugging tohether:

 1. using an extra package that is only used to create simple output to
    the cmd window or the equivalent in the GPS studio program. This
    creates output over the full run the program m makes. By deleting
    the call to the package it is easy todelete all extra statements.
 2. In the case of programs with a GUI using extra calls to that GUI
 3. GDB in situations where it necessary to follow the program statement
    by statement