From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 12/18] Implement completion limiting for sim_command_completer.
Date: Tue, 05 May 2015 15:53:00 -0000 [thread overview]
Message-ID: <5548E771.1020608@redhat.com> (raw)
In-Reply-To: <20150505153422.GS30924@vapier>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/05/2015 08:34 AM, Mike Frysinger wrote:
> that's pretty trivial to get though
>
> $ mkdir build $ cd build $ ../configure --target=ft32-elf $ make
> all-gdb $ ./gdb/gdb (gdb) target sim (gdb) sim <tab>
Sure, and thanks to you [:-)] I did a nearly trivial amount of digging
and found what *might* be a reliable way to test if the test suite is
using a simulator target. mi-support.exp's mi_gdb_target_load tests
"target_info protocol" for "sim".
So looks like I might actually be able to generically write a test for
this.
Thanks for the prodding!
Keith
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVSOdxAAoJEM4/L8mVMm6z/+sP/RfHfZi3Ftw+jJfjmJri7xM6
i2nS5kVlvCd6tCxLIEIW9d8epHqkMK75UsclV7SLuiwjHwh3n4dZUxCP6LpgGLbM
ww2nL46qk3KAzVLI+phIHqso1lZRVbp2cWrS1ipEbfoaRwig3dfeWJX3WLa0pJSa
+tw6rdTZ6kKFqqGh0kTrvVwG3gQNg9vFJ1t/7y10Eug7uswc7SVKA6oxGEuPPspo
R+6GJOkkfL4CfJh9HqztPCd4FdEnG6nn2FILpcVuXeXdVVMw0ls/AMTIltMkXB/V
4pTrtIBQm3mu5jC4NyL+RXdQ+f8u3rqBv9AOm7WRAAF658ic1qqUPcpVUYOPwvOd
xlFg3Wz7f8QZSn6+I8t2bx7YTbdWTEUoQN7h7HQBoFKyZfrs938Rwf2Y+b0udqyi
R8jnaWLEsOfCeZL6qH29O7UUwDsAIL6URMZaddQRHk4q48sO34+7k2gXQnDBMZgw
zzb093al0xPKKD7Qb4xJ4UqG2YGygOScPJTuupiszFLuL8TdQFKFZjDL46XeuD82
RiGd9+XY6hT8nt3zgDReAAy2EoiXq7UASkz87AI1UFzJeV5fanqJKhKIUUeI7+eh
eCLo5lYnNweHoKm1NnvajH8Hm+KmwRT87QgN5W+YJmV8lddBqRXsXI+H6vGYGXe2
ifz5rM+n49gHe6XqAAz5
=+5N5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-05-05 15:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 19:23 [PATCH 00/18] Implement full completer limiting Keith Seitz
2015-04-13 19:23 ` [PATCH 04/18] Implement completion limiting for add_filename_to_list Keith Seitz
2015-04-13 19:23 ` [PATCH 18/18] Remove the vector return result from the completion API Keith Seitz
2015-04-13 19:23 ` [PATCH 02/18] Remove completion_tracker_t from the public " Keith Seitz
2015-04-13 19:23 ` [PATCH 07/18] Implement completion limiting for filename_completer Keith Seitz
2015-04-13 19:23 ` [PATCH 15/18] Implement completion limiting for scmcmd_add_completion Keith Seitz
2015-04-13 19:23 ` [PATCH 05/18] Implement completion limiting for ada_make_symbol_completion_list Keith Seitz
2015-04-13 19:23 ` [PATCH 08/18] Implement completion limiting for signal_completer Keith Seitz
2015-04-13 19:23 ` [PATCH 11/18] Implement completion limiting for reg_or_group_completer Keith Seitz
2015-04-13 19:23 ` [PATCH 12/18] Implement completion limiting for sim_command_completer Keith Seitz
2015-04-14 15:28 ` Mike Frysinger
2015-05-05 15:03 ` Keith Seitz
2015-05-05 15:34 ` Mike Frysinger
2015-05-05 15:53 ` Keith Seitz [this message]
2015-04-13 19:23 ` [PATCH 01/18] Add struct completer_data to the completion API Keith Seitz
2015-04-13 19:23 ` [PATCH 16/18] Make the completion API completely opaque Keith Seitz
2015-04-13 19:23 ` [PATCH 13/18] Implement completion limiting for complete_on_enum Keith Seitz
2015-04-13 19:23 ` [PATCH 17/18] Use the hashtable to accumulate completion results Keith Seitz
2015-04-13 19:23 ` [PATCH 03/18] Implement completion limiting for complete_on_cmdlist Keith Seitz
2015-04-13 19:23 ` [PATCH 09/18] Implement completion limiting for interpreter_completer Keith Seitz
2015-04-13 19:23 ` [PATCH 14/18] Implement completion limiting in add_struct_fields Keith Seitz
2015-04-13 19:23 ` [PATCH 06/18] Implement completion limiting for condition_completer Keith Seitz
2015-04-13 19:23 ` [PATCH 10/18] Implement completion limiting for cmdpy_completer Keith Seitz
2015-04-20 3:21 ` [PATCH 00/18] Implement full completer limiting Doug Evans
2015-04-29 19:19 ` Keith Seitz
2015-04-30 0:26 ` Doug Evans
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=5548E771.1020608@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@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).