Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Hayward <Alan.Hayward@arm.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	nd <nd@arm.com>
Subject: Re: [PATCH v2 1/2] btrace: fix output of "set record btrace"
Date: Tue, 06 Mar 2018 09:34:00 -0000	[thread overview]
Message-ID: <E04EA9A7-607A-4F03-86FD-AA23C0BBB5E5@arm.com> (raw)
In-Reply-To: <A78C989F6D9628469189715575E55B236964FC78@IRSMSX104.ger.corp.intel.com>



> On 5 Mar 2018, at 16:55, Metzger, Markus T <markus.t.metzger@intel.com> wrote:
> 
> Hello Alan,
> 
> Thanks for your review.
> 
>>> Instead of giving a message that "set record btrace" needs a
>>> sub-command, GDB crashed.  Fix it.  A regression test comes with the next
>> patch.
>>> 
>>> 2018-03-05  Markus Metzger  <markus.t.metzger@intel.com>
>>> 
>>> gdb/
>>> 	* record-btrace.c (cmd_set_record_btrace): Print sub-commands.
>>> ---
>>> gdb/record-btrace.c | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>> 
>>> diff --git a/gdb/record-btrace.c b/gdb/record-btrace.c index
>>> 48eda54..905f0c4 100644
>>> --- a/gdb/record-btrace.c
>>> +++ b/gdb/record-btrace.c
>>> @@ -2953,7 +2953,10 @@ cmd_record_btrace_start (const char *args, int
>>> from_tty) static void cmd_set_record_btrace (const char *args, int
>>> from_tty) {
>>> -  cmd_show_list (set_record_btrace_cmdlist, from_tty, "");
>>> +  printf_unfiltered (_("\"set record btrace\" must be followed "
>>> +		       "by an apporpriate subcommand.\n"));
>> 
>> appropriate not apporpriate.
> 
> Thanks.  I'm adding another patch to the series to fix that same typo in the
> "set record" command from where I took the message.  See below.
> 
> Looks like this text is not used in any test (grep did not find anything),
> except for the new gdb.btrace/cpu.exp that 2/2 of this series adds.
> 

New patch LGTM.


> Regards,
> Markus.
> 
> ---
> 
> commit 755376c12a2fa53d8304ff68265a09b8a332e965
> Author: Markus Metzger <markus.t.metzger@intel.com>
> Date:   Mon Mar 5 17:44:57 2018 +0100
> 
>    record: fix typo in "set record" output
> 
>    Alan Hayward pointed out a typo in the output of "set record btrace" that
>    I took from "set record".  Fix the original.
> 
>    Signed-off-by: Markus Metzger  <markus.t.metzger@intel.com>
> 
>    gdb/
>        * record.c (set_record_command): Fix typo in message.
> 
> diff --git a/gdb/record.c b/gdb/record.c
> index cd83b99..aec2be3 100644
> --- a/gdb/record.c
> +++ b/gdb/record.c
> @@ -320,7 +320,7 @@ static void
> set_record_command (const char *args, int from_tty)
> {
>   printf_unfiltered (_("\"set record\" must be followed "
> -                      "by an apporpriate subcommand.\n"));
> +                      "by an appropriate subcommand.\n"));
>   help_list (set_record_cmdlist, "set record ", all_commands, gdb_stdout);
> }
> 
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
> 


      reply	other threads:[~2018-03-06  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 10:59 Markus Metzger
2018-03-05 10:59 ` [PATCH v2 2/2] btrace: set/show record btrace cpu Markus Metzger
2018-03-05 16:16   ` Eli Zaretskii
2018-03-05 16:35 ` [PATCH v2 1/2] btrace: fix output of "set record btrace" Alan Hayward
2018-03-05 16:55   ` Metzger, Markus T
2018-03-06  9:34     ` Alan Hayward [this message]

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=E04EA9A7-607A-4F03-86FD-AA23C0BBB5E5@arm.com \
    --to=alan.hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=nd@arm.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