Hi, I've found some errors in gdb which make it unable to step into or
over certain functions. Specifically, when I try to step into these
functions gdb jumps to some random functions (always the last line in a
file) without even making an ew stack frame... it just overwrites the
existing one!! Then, if I try to go on (or if I just try to step over
the function) gdb just continues as if I had pressed "c".
My gdb is 4.16-6 precompiled from RedHat for RedHat 4.2. (And I'm
running 2.0.30 on a PPro with gcc-220.127.116.11) Firstly, I was suspicious
about the suposed "fixes" to gdb (6 of them!) I can't find much info on
these, and GNU doesn't seem to have added any of them to the official
distribution... are they really good, or might they be causing my bug?
Also, I wonder if my bug might be caused by Red Hat's providing a binary
that is linked or compiled with old binutils.
Has anyone else had problems with gdb jumping to the wrong place? (I
had another problem before, when g++ emitted code for a default
operator=, got it mixed up with MY operator=, and then tried to let gdb
step into ITs operator= :) If there is a better place to discuss this,
or any good place for finding gdb info, please let me know.
Anyone know if a new release is expected anytime soon?