From: Richard Earnshaw <Richard.Earnshaw@buzzard.freeserve.co.uk>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH v2] gdb: sim: add command line completion
Date: Sat, 16 Apr 2011 11:40:00 -0000 [thread overview]
Message-ID: <4DA97EF5.7070603@buzzard.freeserve.co.uk> (raw)
In-Reply-To: <1302837600-23098-1-git-send-email-vapier@gentoo.org>
On 15/04/11 04:20, Mike Frysinger wrote:
> For now, only the sub-command name is completed. No support yet for
> completing options to that command. But even this is a huge step as
> currently, nothing is completed, and the basic "help sim" is fairly
> obtuse as to what exactly the "sim" command accepts.
>
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
>
> gdb/:
> 2011-04-07 Mike Frysinger <vapier@gentoo.org>
>
> * remote-sim.c (sim_command_completer): New function.
> (_initialize_remote_sim): Set completer to sim_command_completer.
>
> include/gdb/:
> 2011-04-07 Mike Frysinger <vapier@gentoo.org>
>
> * remote-sim.h (sim_complete_command): New prototype.
>
> sim/:
> 2011-04-07 Mike Frysinger <vapier@gentoo.org>
>
> * sim-options.c (complete_option_list, sim_complete_command):
> New functions.
This breaks building gdb for arm-eabi.
/home/rearnsha/gnusrc/gcc-cross/git/gdb/remote-sim.c:1205: undefined
reference to `sim_complete_command'
Note the ARM simulator doesn't use most of the sim/common infrastructure.
R.
next prev parent reply other threads:[~2011-04-16 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 23:32 [PATCH] " Mike Frysinger
2011-04-14 20:02 ` Tom Tromey
2011-04-15 3:44 ` [toolchain-devel] " Mike Frysinger
2011-04-19 17:13 ` Tom Tromey
2011-04-15 3:20 ` [PATCH v2] " Mike Frysinger
2011-04-16 11:40 ` Richard Earnshaw [this message]
2011-04-16 18:33 ` Mike Frysinger
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=4DA97EF5.7070603@buzzard.freeserve.co.uk \
--to=richard.earnshaw@buzzard.freeserve.co.uk \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.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