Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH 5/5] btrace: maintenance commands
Date: Tue, 30 Jun 2015 12:57:00 -0000	[thread overview]
Message-ID: <5592921E.4060009@redhat.com> (raw)
In-Reply-To: <1435047418-21611-6-git-send-email-markus.t.metzger@intel.com>

On 06/23/2015 09:16 AM, Markus Metzger wrote:
> Add maintenance commands that help debugging the btrace record target.
> The following new commands are added:

Looks good to me, with the minor nits pointed out below addressed.


>  }
> @@ -2192,3 +2235,682 @@ make_cleanup_btrace_data (struct btrace_data *data)
>  {
>    return make_cleanup (do_btrace_data_cleanup, data);
>  }
> +
> +#if defined (HAVE_LIBIPT)
> +
> +/* Print a single packet.  */
> +
> +static void
> +pt_print_packet (const struct pt_packet *packet)
> +{
> +  switch (packet->type)
> +    {
> +    default:
> +      printf_unfiltered ("[??: %x]", packet->type);

I think the missing _() will result in ARI warnings.
You can use extra ()'s to suppress them, like:

     printf_unfiltered (("[??: %x]"), packet->type);


> +      break;
> +
> +    case ppt_psb:
> +      printf_unfiltered ("psb");
> +      break;

etc.

> +btrace clear-packet-history' to clear and recompute the existing history."),
> +			   NULL, NULL, &maint_btrace_pt_set_cmdlist,
> +			   &maint_btrace_pt_show_cmdlist);

Please add a show callback.

Thanks,
Pedro Alves


  parent reply	other threads:[~2015-06-30 12:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23  8:22 [PATCH 0/5] Support Intel(R) Processor Trace Markus Metzger
2015-06-23  8:22 ` [PATCH 1/5] configure: check for libipt Markus Metzger
2015-06-30 12:56   ` Pedro Alves
2015-06-30 14:54     ` Metzger, Markus T
2015-06-30 15:01       ` Pedro Alves
2015-06-23  8:22 ` [PATCH 5/5] btrace: maintenance commands Markus Metzger
2015-06-23 15:28   ` Eli Zaretskii
2015-06-24  7:05     ` Metzger, Markus T
2015-06-24 14:38       ` Eli Zaretskii
2015-06-30 12:57   ` Pedro Alves [this message]
2015-06-23  8:22 ` [PATCH 4/5] btrace: store raw btrace data Markus Metzger
2015-06-30 12:56   ` Pedro Alves
2015-06-23  8:22 ` [PATCH 3/5] btrace, linux: use data_size and data_offset Markus Metzger
2015-06-30 12:56   ` Pedro Alves
2015-06-23  8:23 ` [PATCH 2/5] btrace: support Intel(R) Processor Trace Markus Metzger
2015-06-23 15:32   ` Eli Zaretskii
2015-06-30 12:56   ` Pedro Alves
2015-06-30 14:54     ` Metzger, Markus T
2015-06-30 15:08       ` Pedro Alves
2015-07-01  8:39         ` 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=5592921E.4060009@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.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