From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Kevin Buettner <kevinb@redhat.com>
Subject: Re: Should we be able to read simulator memory immediately after a "load" command?
Date: Mon, 28 Jun 2010 22:28:00 -0000 [thread overview]
Message-ID: <201006281827.38228.vapier@gentoo.org> (raw)
In-Reply-To: <20100628130010.360f398d@mesquite.lan>
[-- Attachment #1: Type: Text/Plain, Size: 225 bytes --]
On Monday, June 28, 2010 16:00:10 Kevin Buettner wrote:
> So, the obvious question... Is there any good reason to prohibit
> access to the simulator's memory immediately after a load?
i'd like this restriction removed
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-06-28 22:28 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 [this message]
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=201006281827.38228.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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