This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: PRecord sets memory even when it says it did not
- From: Daniel Jacobowitz <drow at false dot org>
- To: Hui Zhu <teawater at gmail dot com>
- Cc: Marc Khouzam <marc dot khouzam at ericsson dot com>, "gdb at sourceware dot org" <gdb at sourceware dot org>, Michael Snyder <msnyder at vmware dot com>, gdb-patches ml <gdb-patches at sourceware dot org>
- Date: Mon, 14 Sep 2009 11:53:27 -0400
- Subject: Re: PRecord sets memory even when it says it did not
- References: <F7CE05678329534C957159168FA70DEC5153600749@EUSAACMS0703.eamcs.ericsson.se> <daef60380909132139k46f577aet63f4089a97138368@mail.gmail.com>
On Mon, Sep 14, 2009 at 12:39:35PM +0800, Hui Zhu wrote:
> > (gdb) set var a = 8
> > Because GDB is in replay mode, writing to memory will make the execution log unusable from this point onward. ?Write memory at address 0xbffff6a0?(y or [n]) n
> > Process record canceled the operation.
> > (gdb) p a
> > $2 = 8
This should refetch the value from the target. What value is cached?
> 2009-09-14 Hui Zhu <teawater@gmail.com>
>
> * record.c (record_xfer_partial): Call free_all_values when
> cancel the operation.
I don't think this is a good idea; this is a memory management
function. It's not supposed to change the apparent values.
--
Daniel Jacobowitz
CodeSourcery