From: Pedro Alves <palves@redhat.com>
To: Steve Ellcey <sellcey@imgtec.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch, simulator] Fix sim_command_completer arguments.
Date: Fri, 15 Mar 2013 18:27:00 -0000 [thread overview]
Message-ID: <5143619F.9040701@redhat.com> (raw)
In-Reply-To: <2642b17f-5e3b-41b2-a985-ffcaa9220e95@BAMAIL02.ba.imgtec.org>
On 03/15/2013 05:31 PM, Steve Ellcey wrote:
> My build of gdb and sim have recently started failing with:
>
> /local/home/sellcey/nightly2/src/gdb/gdb/remote-sim.c: In function '_initialize_remote_sim':
> /local/home/sellcey/nightly2/src/gdb/gdb/remote-sim.c:1323: error: passing argument 2 of 'set_cmd_completer' from incompatible pointer type
> /local/home/sellcey/nightly2/src/gdb/gdb/command.h:161: note: expected 'struct VEC_char_ptr * (*)(struct cmd_list_element *, const char *, const char *)' but argument is of type 'struct VEC_char_ptr * (*)(struct cmd_list_element *, char *, char *)'
>
> I didn't see any change in gdb/sim that might be causing this but I am
> building with the latest (ToT) GCC and I think a change there might have
> caused GCC to start catching this discrepency in argument types.
Actually, the completers prototype only got that "const" this week, and
I missed that there were completers in the sim:
http://sourceware.org/ml/gdb-patches/2013-03/msg00572.html
Sorry about that.
> I would
> like to fix it by adding the 'const' modifier to the sim_command_completer
> text and word arguments so that its argument types match filename_completer,
> expression_completer, etc.
That's the right fix, thanks.
--
Pedro Alves
prev parent reply other threads:[~2013-03-15 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 17:37 Steve Ellcey
2013-03-15 17:50 ` Tom Tromey
2013-03-15 17:55 ` Michael Eager
2013-03-15 18:01 ` Mike Frysinger
2013-03-15 18:27 ` Pedro Alves [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=5143619F.9040701@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sellcey@imgtec.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