From: Eli Zaretskii <eliz@gnu.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: palves@redhat.com, jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [rfc] btrace: control memory access during replay
Date: Fri, 04 Apr 2014 09:48:00 -0000 [thread overview]
Message-ID: <8338hta0hm.fsf@gnu.org> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B230C148832@IRSMSX104.ger.corp.intel.com>
> From: "Metzger, Markus T" <markus.t.metzger@intel.com>
> CC: "palves@redhat.com" <palves@redhat.com>, "jan.kratochvil@redhat.com"
> <jan.kratochvil@redhat.com>, "gdb-patches@sourceware.org"
> <gdb-patches@sourceware.org>
> Date: Fri, 4 Apr 2014 09:42:46 +0000
>
> > Other than that, the documentation parts are approved. However, I
> > wonder whether "allow-memory-access" is a good name for a setting
> > which actually allows access to writable portion of the memory. IOW,
> > even when the value is OFF, we do allow access to memory, just not the
> > writable portion of it.
>
> Agreed; allow-access-to-writable-memory-while-replaying is a bit long, though.
How about access-writable-memory?
next prev parent reply other threads:[~2014-04-04 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:56 Markus Metzger
2014-04-04 9:16 ` Eli Zaretskii
2014-04-04 9:44 ` Metzger, Markus T
2014-04-04 9:48 ` Eli Zaretskii [this message]
2014-05-14 15:35 ` Pedro Alves
2014-05-19 7:51 ` Metzger, Markus T
2014-05-19 17:44 ` Pedro Alves
2014-05-20 7:01 ` Metzger, Markus T
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=8338hta0hm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=markus.t.metzger@intel.com \
--cc=palves@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