From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrea Monaco <andrea.monaco@autistici.org>, gdb@sourceware.org
Subject: Re: [PATCH] gnu-nat.c: fix calls to add_info_alias
Date: Mon, 22 Nov 2021 21:32:48 -0500 [thread overview]
Message-ID: <381c7713-74e5-de35-0ff2-5af1c50d1996@polymtl.ca> (raw)
In-Reply-To: <87h7cp8dae.fsf@autistici.org>
On 2021-11-06 12:22, Andrea Monaco via Gdb wrote:
>
> Hello,
>
>
> some time ago add_info_alias was changed (commit
> e0f25bd9717c7973197095523db7c1cdc956cea2). These calls were not updated
> and caused errors on compilation.
>
>
> Warmly,
>
> Andrea Monaco
>
>
>
> diff --git a/gdb/gnu-nat.c b/gdb/gnu-nat.c
> index c6cecff0686..2d15b3d3e58 100644
> --- a/gdb/gnu-nat.c
> +++ b/gdb/gnu-nat.c
> @@ -3286,15 +3286,17 @@ This is the same as setting `task pause', `exceptions', and\n\
> _("Show information about the task's send rights."));
> add_info ("receive-rights", info_recv_rights_cmd,
> _("Show information about the task's receive rights."));
> - add_info ("port-rights", info_port_rights_cmd,
> - _("Show information about the task's port rights."));
> - add_info ("port-sets", info_port_sets_cmd,
> - _("Show information about the task's port sets."));
> + cmd_list_element *port_rights_cmd =
> + add_info ("port-rights", info_port_rights_cmd,
> + _("Show information about the task's port rights."));
> + cmd_list_element *port_sets_cmd =
> + add_info ("port-sets", info_port_sets_cmd,
> + _("Show information about the task's port sets."));
> add_info ("dead-names", info_dead_names_cmd,
> _("Show information about the task's dead names."));
> - add_info_alias ("ports", "port-rights", 1);
> - add_info_alias ("port", "port-rights", 1);
> - add_info_alias ("psets", "port-sets", 1);
> + add_info_alias ("ports", port_rights_cmd, 1);
> + add_info_alias ("port", port_rights_cmd, 1);
> + add_info_alias ("psets", port_sets_cmd, 1);
> }
>
> ^L
>
Hi,
I had trouble applying your patch, I suppose the text was modified by
your email client. But it is small enough that I applied it by hand and
pushed it, thanks. Just note for next time that patches should ideally
be sent to the gdb-patches mailing list.
Simon
prev parent reply other threads:[~2021-11-23 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 16:22 Andrea Monaco
2021-11-23 2:32 ` Simon Marchi [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=381c7713-74e5-de35-0ff2-5af1c50d1996@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=andrea.monaco@autistici.org \
--cc=gdb@sourceware.org \
/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).