From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "gdb-patches\@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA] completer test [was Re: [RFC] Cleanup for make_source_files_completion_list]
Date: Wed, 15 May 2013 22:33:00 -0000 [thread overview]
Message-ID: <m3r4h7kh4p.fsf@redhat.com> (raw)
In-Reply-To: <5193E2DC.5000200@redhat.com> (Keith Seitz's message of "Wed, 15 May 2013 12:32:44 -0700")
Hi Keith,
I know you have already committed the patch, but I just would like to
ask a few things.
On Wednesday, May 15 2013, Keith Seitz wrote:
> diff --git a/gdb/testsuite/gdb.base/filesym.exp b/gdb/testsuite/gdb.base/filesym.exp
> new file mode 100644
> index 0000000..c9e9c20
> --- /dev/null
> +++ b/gdb/testsuite/gdb.base/filesym.exp
> +# Test completion list for "filesy". We expect the immediate result to
> +# complete to "filesym"; completing again, we expect the symbol name and the
> +# filename (in that order).
> +
> +send_gdb "break filesy\t"
> +gdb_expect {
> + -re "m\$" {
> + pass "complete on \"filesy\""
> +
> + # Now ask for the completion list
> + send_gdb "\t\t"
> + gdb_expect {
> + -re ".*filesym\[ \t\]+filesym.c.*$gdb_prompt break filesym\$" {
> + pass "completion list for \"filesym\""
> + }
> +
> + default {
> + fail "completion list for \"filesym\""
> + }
> + }
> + }
> +
> + default {
> + fail "complete on \"filesy\""
> + }
> +}
Wouldn't it be better to use the "complete" command? Here is what I see
when I use it:
(gdb) complete break filesy
break filesym
break filesym.c
Also, ISTR "send_gdb" is deprecated, and one should use
"gdb_test_multiple" instead. WDYT?
Thanks,
--
Sergio
next prev parent reply other threads:[~2013-05-15 22:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 19:46 [RFC] Cleanup for make_source_files_completion_list Keith Seitz
2013-05-09 20:58 ` Tom Tromey
2013-05-09 23:45 ` Doug Evans
2013-05-13 18:42 ` Keith Seitz
2013-05-13 21:11 ` Keith Seitz
2013-05-15 17:36 ` Keith Seitz
2013-05-15 19:32 ` [RFA] completer test [was Re: [RFC] Cleanup for make_source_files_completion_list] Keith Seitz
2013-05-15 20:01 ` Tom Tromey
2013-05-15 21:22 ` Keith Seitz
2013-05-15 22:33 ` Sergio Durigan Junior [this message]
2013-05-15 23:47 ` Keith Seitz
2013-05-16 0:21 ` Sergio Durigan Junior
2013-05-16 0:27 ` Stan Shebs
2013-05-16 9:38 ` Pedro Alves
2013-05-16 5:30 ` Joel Brobecker
2013-05-16 5:49 ` Joel Brobecker
2013-05-16 15:41 ` Keith Seitz
2013-05-17 5:14 ` Joel Brobecker
2013-05-17 16:27 ` Tom Tromey
2013-05-20 5:28 ` Joel Brobecker
2013-05-20 14:47 ` Tom Tromey
2013-05-21 5:43 ` Checked in: " Joel Brobecker
2013-05-21 5:44 ` Joel Brobecker
2013-05-16 5:53 ` Sergio Durigan Junior
2013-05-16 6:00 ` Joel Brobecker
2013-05-16 9:19 ` Pedro Alves
2013-05-16 9:26 ` Joel Brobecker
2013-05-16 10:18 ` Pedro Alves
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=m3r4h7kh4p.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.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