Re: Debugger Rant (was Re: How to debug an Ada program)

[Wesley Groleau <wesgroleau@despammed.com>]

Marc A. Criley wrote:
> Based on my experience helping other developers debug their code, I've
> found a disconcertedly common trend when it comes to using debuggers. 
> Very few know how to use one effectively--and this goes not just for
> Ada programmers, but programmers in general.  The most common
> perception of a debugger I've seen held by programmers is that it's
> for single-stepping through code and setting breakpoints; and for the
> advanced user, examining variables.  On several occasions when
> assisting other developers I've opened up the raw memory display
> window, or even (gasp!) the register or disassembly windows, and the
> look on the programmer's face is utter incomprehension (which may also

Well, I could say all of the same things, BUT I can also say
there have been numerous occasions where a description of
the symptoms and a glance at the source code have enabled me
to identify the problem.  There are just so many more things
that can go wrong in a C program that won't happen in Ada.

And there have been more than a few occasions where invoking
the debugger makes the problem go away!

And there have been occasions where the debugger added a problem
or deceived us by not telling the truth about the value of an entity,
or getting the address wrong on an interactive assignment.

> Considering a debugger to be superfluous to Ada programming deprives
> one of a very powerful tool.  Unless all you're ever going to do is

True.