gdb code review, pointer madness

[Jim Blandy]

On 1/24/06, NZG <ngustavson@emacinc.com> wrote:
> Looks like this particular flaw is an optimization trick, digging down farther
> the correct pointer does appear to get there.
>
> Something is wrong with the frame call on the sential frame (because it
> crashes the debugger) but this is not it.

Well, if you are able to come up with some reproduction instructions
that don't require exotic hardware, let us know.

The sentinel frame should be very simple to deal with: "unwinding" a
register from the sentinel frame simply returns its current value from
the chip.  If you're not getting the current registers' values unwound
from the sentinel frame, then GDB simply isn't getting the register
values right; you'll need to look at the communication between GDB and
the board.