From: Tom Tromey <tom@tromey.com>
To: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Luis Machado <luis.machado@arm.com>
Subject: Re: [PATCH] Fix crash with "maintenance print arc"
Date: Fri, 27 May 2022 07:34:45 -0600 [thread overview]
Message-ID: <871qwf6qve.fsf@tromey.com> (raw)
In-Reply-To: <06f43b22-c740-860b-1c75-9a00dcff12da@arm.com> (Luis Machado via Gdb-patches's message of "Thu, 5 May 2022 10:31:09 +0100")
>>>>> "Luis" == Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
>> - add_show_prefix_cmd ("arc", class_maintenance,
>> - _("ARC-specific maintenance commands for printing GDB "
>> - "internal state."),
>> - &maintenance_print_arc_list,
>> - 0, &maintenanceprintlist);
>> + add_basic_prefix_cmd ("arc", class_maintenance,
>> + _("ARC-specific maintenance commands for printing GDB "
>> + "internal state."),
>> + &maintenance_print_arc_list,
>> + 0, &maintenanceprintlist);
>> add_cmd ("arc-instruction", class_maintenance,
>> dump_arc_instruction_command,
Luis> FTR, I'm happy to go with your patch for this one.
Oops, I dropped this. I will check it in shortly.
Tom
prev parent reply other threads:[~2022-05-27 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:07 Luis Machado
2022-04-27 10:43 ` Andrew Burgess
2022-04-27 11:00 ` Luis Machado
2022-04-28 15:27 ` Tom Tromey
2022-04-29 10:20 ` Andrew Burgess
2022-04-28 15:26 ` Tom Tromey
2022-04-29 8:58 ` Luis Machado
2022-04-29 10:18 ` Andrew Burgess
2022-04-29 10:39 ` Luis Machado
2022-04-29 11:25 ` Pedro Alves
2022-05-05 9:31 ` Luis Machado
2022-05-27 13:34 ` Tom Tromey [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=871qwf6qve.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).