From: Simon Marchi <simark@simark.ca>
To: "Jan (janneke) Nieuwenhuizen" <janneke@gnu.org>, gdb@sourceware.org
Subject: Re: [PATCH 3/3] gdb: More compile fixes for gnu-nat.c.
Date: Mon, 22 Nov 2021 10:17:13 -0500 [thread overview]
Message-ID: <9225658f-a554-1ac1-075b-a2f0ea289313@simark.ca> (raw)
In-Reply-To: <20211122073057.19946-1-janneke@gnu.org>
On 2021-11-22 2:30 a.m., Jan (janneke) Nieuwenhuizen via Gdb wrote:
> This fixes compile errors like
>
> ../../gdb-11.1/gdb/gnu-nat.c: In function ‘void add_task_commands()’:
> ../../gdb-11.1/gdb/gnu-nat.c:3204:17: error: no matching function for call to ‘add_cmd(const char [8], command_class, cmd_list_element*&, char*, cmd_list_element**)’
> 3204 | &setlist);
> | ^
> In file included from ../../gdb-11.1/gdb/completer.h:21,
> from ../../gdb-11.1/gdb/symtab.h:36,
> from ../../gdb-11.1/gdb/infrun.h:21,
> from ../../gdb-11.1/gdb/target.h:42,
> from ../../gdb-11.1/gdb/inf-child.h:23,
> from ../../gdb-11.1/gdb/gnu-nat.h:38,
> from ../../gdb-11.1/gdb/gnu-nat.c:24:
> ../../gdb-11.1/gdb/command.h:160:33: note: candidate: ‘cmd_list_element* add_cmd(const char*, command_class, void (*)(const char*, int), const char*, cmd_list_element**)’
> 160 | extern struct cmd_list_element *add_cmd (const char *, enum command_class,
> | ^~~~~~~
> ../../gdb-11.1/gdb/command.h:161:30: note: no known conversion for argument 3 from ‘cmd_list_element*’ to ‘void (*)(const char*, int)’
> 161 | cmd_const_cfunc_ftype *fun,
> | ~~~~~~~~~~~~~~~~~~~~~~~^~~
> ../../gdb-11.1/gdb/command.h:167:33: note: candidate: ‘cmd_list_element* add_cmd(const char*, command_class, const char*, cmd_list_element**)’
> 167 | extern struct cmd_list_element *add_cmd (const char *, enum command_class,
> | ^~~~~~~
> ../../gdb-11.1/gdb/command.h:167:33: note: candidate expects 4 arguments, 5 provided
> ../../gdb-11.1/gdb/gnu-nat.c:3210:18: error: no matching function for call to ‘add_cmd(const char [8], command_class, cmd_list_element*&, char*, cmd_list_element**)’
> 3210 | &showlist);
> | ^
Hi Jan,
I only see patch 3/3, is it normal? Otherwise, patches should be sent
to the gdb-patches mailing list (same address, just with gdb-patches
instead of gdb).
> * gdb/gnu-nat.c (add_task_commands): Use a fresh variable instead of
> shadowing set_signals_cmd etc.
> (add_thread_commands): Likewise.
Note that we don't use ChangeLogs in gdb/.
Simon
next prev parent reply other threads:[~2021-11-22 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 7:30 Jan (janneke) Nieuwenhuizen
2021-11-22 15:17 ` Simon Marchi [this message]
2021-11-22 19:24 ` Jan Nieuwenhuizen
2021-11-23 2:35 ` Simon Marchi
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=9225658f-a554-1ac1-075b-a2f0ea289313@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=janneke@gnu.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).