PRecord sets memory even when it says it did not

[Marc Khouzam]

> -----Original Message-----
> From: Greg Law [mailto:glaw@undo-software.com] 
> Sent: Monday, September 14, 2009 1:11 PM
> To: Hui Zhu
> Cc: Marc Khouzam; gdb@sourceware.org; Michael Snyder; gdb-patches ml
> Subject: Re: PRecord sets memory even when it says it did not
> 
...
> 
> 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).

This does seem to be a recent problem because Hui had fixed it
on July 20th and now it is broken again:
http://sourceware.org/ml/gdb-patches/2009-07/msg00504.html