This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 1/3] 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, gdb-patches at sourceware dot org
- Date: Wed, 21 May 2014 18:12:44 +0300
- Subject: Re: [PATCH v2 1/3] btrace: control memory access during replay
- Authentication-results: sourceware.org; auth=none
- References: <1400587236-18836-1-git-send-email-markus dot t dot metzger at intel dot com> <83fvk4bf9u dot fsf at gnu dot org> <A78C989F6D9628469189715575E55B230C16FA13 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>, "gdb-patches@sourceware.org"
> <gdb-patches@sourceware.org>
> Date: Wed, 21 May 2014 06:09:59 +0000
>
> > > +Control the behavior of the @code{btrace} recording method when
> >
> > Please be consistent about the markup of "btrace": either plain text
> > or @code{}; pick one and use it everywhere.
>
> I'm using @code{btrace} when referring to the record target or recording
> method, and I'm using just btrace when referring to a GDB command.
> I hope that's OK.
GDB commands also get the @code markup.
> I fixed one inconsistency I added with this patch.
I hope that was with "btrace record target".