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

[Michael Snyder <msnyder at vmware dot com>]

Marc Khouzam wrote:
>  
>
> > -----Original Message-----
> > From: Hui Zhu [mailto:teawater@gmail.com] 
> > Sent: Monday, September 14, 2009 12:40 AM
> > To: Marc Khouzam
> > Cc: gdb@sourceware.org; Michael Snyder; gdb-patches ml
> > Subject: Re: PRecord sets memory even when it says it did not
> ...
> > Hi Marc,
> >
> > Thanks for your help.
> >
> > I just tried change it with "p a=99".  I think it must have something
> > different with "set var a = 8".
>
> I also tried it with p a=8 and in my case, the same things happens:
> the memory is changed.
>
> > This issue is because some value cache about the memory.  So I add a
> > "free_all_values ();" before error.
> > It looks OK now.  Please help me try it.
>
> I tried with the patch and it did not fix the problem.
> Let me know if I can do anything to help debug.
> I'm seing this on both SLED and Ubuntu.

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...

Michael