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: "Metzger, Markus T" <markus dot t dot metzger at intel dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: "palves at redhat dot com" <palves at redhat dot com>, "jan dot kratochvil at redhat dot com" <jan dot kratochvil at redhat dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Fri, 4 Apr 2014 09:42:46 +0000
- 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>
> -----Original Message-----
> From: Eli Zaretskii [mailto:eliz@gnu.org]
> Sent: Friday, April 04, 2014 11:17 AM
> The ChangeLog entry should state the name(s) of the node(s) in which
> you make changes.
Thanks, will add it.
> 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.
Let's hear what others say about the feature in general. I remember that
Jan requested something like this. If the feature itself is approved, I'll
try to find a better name.
regards,
markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052