This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] btrace: control memory access during replay
- From: Eli Zaretskii <eliz at gnu dot org>
- To: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- Cc: palves at redhat dot com, jan dot kratochvil at redhat dot com, gdb-patches at sourceware dot org
- Date: Fri, 04 Apr 2014 12:48:53 +0300
- Subject: Re: [rfc] btrace: control memory access during replay
- Authentication-results: sourceware.org; auth=none
- References: <1396601781-25010-1-git-send-email-markus dot t dot metzger at intel dot com> <8361mpa1z9 dot fsf at gnu dot org> <A78C989F6D9628469189715575E55B230C148832 at IRSMSX104 dot ger dot corp dot intel dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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?