From: Daniel Jacobowitz <drow@false.org>
To: Hui Zhu <teawater@gmail.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Michael Snyder <msnyder@vmware.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: PRecord sets memory even when it says it did not
Date: Mon, 14 Sep 2009 15:53:00 -0000 [thread overview]
Message-ID: <20090914155327.GA26740@caradoc.them.org> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2009-09-14 15:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7CE05678329534C957159168FA70DEC5153600749@EUSAACMS0703.eamcs.ericsson.se>
2009-09-14 4:40 ` Hui Zhu
2009-09-14 13:52 ` Marc Khouzam
2009-09-14 17:17 ` Michael Snyder
2009-09-14 17:21 ` Marc Khouzam
2009-09-14 17:26 ` Michael Snyder
2009-09-14 15:53 ` Daniel Jacobowitz [this message]
2009-09-14 16:15 ` Hui Zhu
2009-09-14 17:10 ` Marc Khouzam
2009-09-14 17:10 ` Greg Law
2009-09-14 17:19 ` Marc Khouzam
2009-09-14 17:50 ` Pedro Alves
2009-09-14 17:54 ` Marc Khouzam
2009-09-14 18:00 ` Michael Snyder
2009-09-14 18:01 ` Pedro Alves
2009-09-14 18:02 ` Michael Snyder
2009-09-14 18:15 ` Pedro Alves
2009-09-14 18:21 ` Michael Snyder
2009-09-14 18:36 ` Pedro Alves
2009-09-14 19:04 ` Doug Evans
2009-09-14 19:08 ` Michael Snyder
2009-09-14 20:36 ` Pedro Alves
2009-09-14 21:08 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090914155327.GA26740@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox