Re: info on "value being assigned to is no longer active" error

Siva Velusamy
2008-01-19T04:26:41Z

On Jan 18, 2008 8:21 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Jan 18, 2008 at 08:11:34PM -0800, Siva Velusamy wrote:
> > If my (admittedly cursory) examination of the code in valops.c is
> > correct, it appears as if gdb is looking for the frame to make sure
> > that it updates the value of the register if it has been stored in the
> > stack. Is that correct?
>
> Roughly. All registers in GDB belong to a frame. Either the current
> frame or a saved stack frame. GDB has found the current frame, but
> confuses its ID with an invalid frame marker.
>

Thanks. Should gdb be able to handle this correctly, or is this a
situation where it is tough to define the correct course of action?

If gdb should handle this, what sort of change would be appropriate in
the target specific code?

Siva