Re: PRecord sets memory even when it says it did not

[Pedro Alves <pedro@codesourcery.com>]

On Monday 14 September 2009 18:10:40, Greg Law wrote:
> Hui Zhu wrote:
> > On Mon, Sep 14, 2009 at 09:54, Marc Khouzam <marc.khouzam@ericsson.com> wrote:
> > I just tried change it with "p a=99".  I think it must have something
> > different with "set var a = 8".
> 
> I've noticed something similar with UndoDB.  Until very recently, if we
> failed a 'poke' operation (which we do when in replay mode) the data
> would not be changed.  But with a recent gdb built from cvs (as of about 
> two weeks ago), despite UndoDB failing the poke, the value still appears
> to the user to have been written.
> 
> Could this be related to the caching changes that have happened
> recently?  i.e. does the cache get updated even though the underlying
> poke operation failed?  If so, this issue would seem to be wider than
> just prec (and wider than reverse, too).

If so, then there's an easy way to find out: try again with
"set stack-cache off".

-- 
Pedro Alves