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

[Michael Snyder <msnyder@vmware.com>]

Marc Khouzam wrote:
>  
> 
>> -----Original Message-----
>> From: gdb-patches-owner@sourceware.org 
>> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Michael Snyder
>> Sent: Monday, September 14, 2009 1:14 PM
>> To: Marc Khouzam
>> Cc: 'Hui Zhu'; 'gdb-patches ml'
>> Subject: Re: PRecord sets memory even when it says it did not
>>
> ...
> 
>> Mark --
>>
>> By any chance, if you change the memory, and then do
>> (say) a "stepi", does the memory revert to its previous
>> value?  Just wondering...
> 
> I just ried and you are right, after stepi, 
> p a
> shows the previous value.

Right.  So then, the actual memory in the child process
was not changed.  Some kind of local cache was changed,
and when we did "stepi", we flushed the cache.

As Greg Law mentioned, I seem to recall that there have
been some recent changes in memory caching.

Sounds to me as if the cache accepts the change
before the target rejects it.

Michael