🚀 go-pugleaf

I've tried using gdb a lot in the past few days and I'm amazed at how
bug-ridden it is.  Many times, a M-n goes to a line where the control
flow simply cannot (e.g. backup by one line in a sequence of linear
code).  Printing local variables (or function arguments) routinely
fails.  Sometimes M-s does not behave -- it suddenly spurts ahead by
many lines even though it was supposed to move one line.

It's so bad I almost feel I have no debugger.  Normally I have great
respect for software from the FSF but this is terrible.

I'm using gdb 4.6, with gcc 2.2.2 on a Sun MP server running SunOS
4.1.2.  What could be going wrong?

In case it helps, I "often" find that the mistakes of gdb are
replicated by dbx (but not always).  E.g. if gdb refuses to print a
local variable, then dbx will refuse too.

(I've never had the pleasure of using a good debugger with gcc;
neither dbx nor gdb have worked correctly.  :-(
)

        -ans.
-- 
Ajay Shah, (213)749-8133, ajayshah@usc.edu