From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: Should we be able to read simulator memory immediately after a "load" command?
Date: Fri, 02 Jul 2010 23:14:00 -0000 [thread overview]
Message-ID: <20100702161429.02ead111@mesquite.lan> (raw)
In-Reply-To: <20100702094621.757698c1@mesquite.lan>
On Fri, 2 Jul 2010 09:46:21 -0700
Kevin Buettner <kevinb@redhat.com> wrote:
> I'll post it as a two-parter, the first part moves the static globals
> into a per-inferior struct and makes the necessary adjustments to the
> code. The second part will add `has_memory' and `has_all_memory'
> methods in addition to adjusting gdbsim_xfer_inferior_memory(), thus
> fixing the problem that lead me down this path at the outset.
See:
http://sourceware.org/ml/gdb-patches/2010-07/msg00059.html
and
http://sourceware.org/ml/gdb-patches/2010-07/msg00060.html
Kevin
prev parent reply other threads:[~2010-07-02 23:14 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
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 [this message]
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=20100702161429.02ead111@mesquite.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).