From: Michael Snyder <msnyder@vmware.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Should we be able to read simulator memory immediately after a "load" command?
Date: Mon, 28 Jun 2010 23:57:00 -0000 [thread overview]
Message-ID: <4C2936C8.8010002@vmware.com> (raw)
In-Reply-To: <20100628165514.5f408738@mesquite.lan>
Kevin Buettner wrote:
> On Mon, 28 Jun 2010 15:25:00 -0700
> Michael Snyder <msnyder@vmware.com> wrote:
>
>> Hmm, should we substitute "target_has_memory"?
>>
>> Is that set to TRUE after a load?
>
> If default_child_has_memory() is used, which is currently the case for
> the remote-sim target, it will not return TRUE after a "load", but
> before a "run".
Hmmm. That sucks. ;-)
next prev parent reply other threads:[~2010-06-28 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 20:00 Kevin Buettner
2010-06-28 22:25 ` Michael Snyder
2010-06-28 23:55 ` Kevin Buettner
2010-06-28 23:57 ` Michael Snyder [this message]
2010-06-29 0:46 ` Kevin Buettner
2010-06-28 22:28 ` Mike Frysinger
2010-06-29 19:56 ` Daniel Jacobowitz
2010-07-02 16:46 ` Kevin Buettner
2010-07-02 23:14 ` Kevin Buettner
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=4C2936C8.8010002@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.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