This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

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

From: Marc Khouzam <marc dot khouzam at ericsson dot com>
To: "'Michael Snyder'" <msnyder at vmware dot com>
Cc: "'Hui Zhu'" <teawater at gmail dot com>, "'gdb-patches ml'" <gdb-patches at sourceware dot org>
Date: Mon, 14 Sep 2009 13:20:54 -0400
Subject: RE: PRecord sets memory even when it says it did not
References: <F7CE05678329534C957159168FA70DEC5153600749@EUSAACMS0703.eamcs.ericsson.se> <daef60380909132139k46f577aet63f4089a97138368@mail.gmail.com> <F7CE05678329534C957159168FA70DEC515360088D@EUSAACMS0703.eamcs.ericsson.se> <4AAE79F0.2000506@vmware.com>

 

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

Follow-Ups:
- Re: PRecord sets memory even when it says it did not
  - From: Michael Snyder

References:
- Re: PRecord sets memory even when it says it did not
  - From: Hui Zhu
- RE: PRecord sets memory even when it says it did not
  - From: Marc Khouzam
- Re: PRecord sets memory even when it says it did not
  - From: Michael Snyder

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]