From: Doug Evans <xdje42@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3 06/19] Implement completion limiting for condition_completer.
Date: Sun, 23 Aug 2015 03:53:00 -0000 [thread overview]
Message-ID: <m37fomirvj.fsf@sspiff.org> (raw)
In-Reply-To: <20150806191624.32159.8524.stgit@valrhona.uglyboxes.com> (Keith Seitz's message of "Thu, 06 Aug 2015 12:16:45 -0700")
Keith Seitz <keiths@redhat.com> writes:
> There are no changes from the last revision.
>
> --
>
> This patch converts the condition completer to use add_completion.
> A side-effect of this is the similar conversion of complete_internalvar.
>
> Tests have been added to exercise this new behavior.
>
> gdb/ChangeLog
>
> * breakpoint.c (condition_completer): Pass completer_data to
> complete_internalvar.
> Use add_completion.
> * value.c: Include completer.h.
> (complete_internalvar): Add completer_data argument.
> Use add_completion.
> * value.h (complete_internalvar): Add completer_data argument.
>
> gdb/testsuite/ChangeLog
>
> * gdb.base/condbreak.exp (test_completion): New procedure.
> Add more completion tests, with and without limiting.
====
One nit.
Ok with that fixed.
> ---
> gdb/breakpoint.c | 8 +++-
> gdb/testsuite/gdb.base/condbreak.exp | 70 ++++++++++++++++++++++++++++++++++
> gdb/value.c | 9 ++--
> gdb/value.h | 3 +
> 4 files changed, 83 insertions(+), 7 deletions(-)
>
> diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
> index 70569df..24243c4 100644
> --- a/gdb/breakpoint.c
> +++ b/gdb/breakpoint.c
> @@ -1052,7 +1052,7 @@ condition_completer (struct completer_data *cdata,
> /* We don't support completion of history indices. */
> if (isdigit (text[1]))
> return NULL;
> - return complete_internalvar (&text[1]);
> + return complete_internalvar (cdata, &text[1]);
> }
>
> /* We're completing the breakpoint number. */
> @@ -1065,7 +1065,11 @@ condition_completer (struct completer_data *cdata,
> xsnprintf (number, sizeof (number), "%d", b->number);
>
> if (strncmp (number, text, len) == 0)
> - VEC_safe_push (char_ptr, result, xstrdup (number));
> + {
> + if (add_completion (cdata, &result, number, NULL, NULL)
> + == ADD_COMPLETION_MAX_REACHED)
> + break;
> + }
> }
>
> return result;
> diff --git a/gdb/testsuite/gdb.base/condbreak.exp b/gdb/testsuite/gdb.base/condbreak.exp
> index fa40a5f..5630ede 100644
> --- a/gdb/testsuite/gdb.base/condbreak.exp
> +++ b/gdb/testsuite/gdb.base/condbreak.exp
> @@ -246,3 +246,73 @@ gdb_test "complete cond 1" "cond 1"
> gdb_test "set variable \$var = 1"
> gdb_test "complete cond \$v" "cond \\\$var"
> gdb_test "complete cond 1 values\[0\].a" "cond 1 values.0..a_field"
> +
> +# Test non-trivial completion and completion-limiting
> +
> +# Delete all breakpoints and create a bunch of new ones.
> +delete_breakpoints
> +for {set i 0} {$i < 20} {incr i} {
> + with_test_prefix "set breakpoint $i" {
> + gdb_breakpoint "factorial"
> + }
> +}
> +
> +# While the completer function does traverse breakpoints in the order
> +# they were created, don't assume that is required for the test.
> +# We only count the number of completions found. In this case,
> +# this test will create breakpoints 9-19, giving "complete cond 1"
> +# ten total completion possibilities.
> +
> +# A convenience procedure to automate test completion lists.
> +proc test_completion {cmd exp total {limit 0}} {
> + global gdb_prompt
> +
> + if {$limit} {
> + set end "\\\*\\\*\\\* List may be truncated, "
> + append end "max-completions reached\\\. \\\*\\\*\\\*\r\n"
> + set testname "limit '$cmd'"
> + } else {
> + set end ""
> + set testname $cmd
> + }
> +
> + set seen 0
> + gdb_test_multiple $cmd $testname {
> + "$cmd\r\n" { exp_continue }
> +
> + -re "cond $exp\[0-9\]+\r\n" {
> + incr seen
> + exp_continue
> + }
> +
> + -re ".*$end$gdb_prompt $" {
> + if {$seen == $total} {
> + pass $testname
> + } else {
> + fail "$testname ($seen/$total)"
> + }
> + }
> + }
> +}
====
Nice test.
> +
> +# Test completion of breakpoint number.
> +with_test_prefix "completion test:" {
> + test_completion "complete cond 1" "1" 10
> +}
> +
> +# Test completion of breakpoint number using internal variable.
> +for {set i 0} {$i < 10} {incr i} {
> + gdb_test_no_output "set variable \$var_bp_$i = $i"
> +}
> +
> +test_completion "complete cond \$var_bp" "\\\$var_bp_" 10
> +
> +# Run the above tests with completion limiting.
> +set max_completions 4
> +gdb_test_no_output "set max-completions $max_completions"
> +
> +with_test_prefix "completion test:" {
> + test_completion "complete cond 1" "1" $max_completions 1
> +}
> +
> +test_completion "complete cond \$var_bp" "\\\$var_bp_" $max_completions 1
> diff --git a/gdb/value.c b/gdb/value.c
> index 63ee94d..22d392a 100644
> --- a/gdb/value.c
> +++ b/gdb/value.c
> @@ -40,6 +40,7 @@
> #include "tracepoint.h"
> #include "cp-abi.h"
> #include "user-regs.h"
> +#include "completer.h"
>
> /* Prototypes for exported functions. */
>
> @@ -2062,7 +2063,7 @@ lookup_only_internalvar (const char *name)
> were found. */
>
> VEC (char_ptr) *
> -complete_internalvar (const char *name)
> +complete_internalvar (struct completer_data *cdata, const char *name)
> {
> VEC (char_ptr) *result = NULL;
> struct internalvar *var;
> @@ -2073,9 +2074,9 @@ complete_internalvar (const char *name)
> for (var = internalvars; var; var = var->next)
> if (strncmp (var->name, name, len) == 0)
> {
> - char *r = xstrdup (var->name);
> -
> - VEC_safe_push (char_ptr, result, r);
> + if (add_completion (cdata, &result, var->name, NULL, NULL)
> + == ADD_COMPLETION_MAX_REACHED)
> + break;
> }
>
> return result;
> diff --git a/gdb/value.h b/gdb/value.h
> index 82deaf2..03df1b7 100644
> --- a/gdb/value.h
> +++ b/gdb/value.h
> @@ -876,7 +876,8 @@ extern struct internalvar *lookup_only_internalvar (const char *name);
>
> extern struct internalvar *create_internalvar (const char *name);
>
> -extern VEC (char_ptr) *complete_internalvar (const char *name);
> +extern VEC (char_ptr) *complete_internalvar (struct completer_data *cdata,
> + const char *name);
====
Add a forward decl for struct completer_cdata.
>
> /* An internalvar can be dynamically computed by supplying a vector of
> function pointers to perform various operations. */
next prev parent reply other threads:[~2015-08-23 3:53 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 2:37 [PATCH v3 00/19] New completer API Keith Seitz
2015-08-06 19:18 ` [PATCH v3 09/19] Implement completion limiting for interpreter_completer Keith Seitz
2015-08-23 4:03 ` Doug Evans
2015-08-06 19:20 ` [PATCH v3 12/19] Implement completion limiting for sim_command_completer Keith Seitz
2015-08-23 4:11 ` Doug Evans
2015-08-06 19:58 ` [PATCH v3 06/19] Implement completion limiting for condition_completer Keith Seitz
2015-08-23 3:53 ` Doug Evans [this message]
2015-08-06 19:58 ` [PATCH v3 18/19] Use the hashtable to accumulate completion results Keith Seitz
2015-08-23 17:53 ` Doug Evans
2015-08-06 19:58 ` [PATCH v3 19/19] Remove the vector return result from the completion API Keith Seitz
2015-08-23 18:03 ` Doug Evans
2015-08-06 19:58 ` [PATCH v3 02/19] Remove completion_tracker_t from the public " Keith Seitz
2015-08-23 1:02 ` Doug Evans
2015-08-24 16:06 ` Doug Evans
2015-08-06 19:58 ` [PATCH v3 04/19] Implement completion limiting for add_filename_to_list Keith Seitz
2015-08-23 1:07 ` Doug Evans
2015-08-06 20:03 ` [PATCH v3 01/19] Add struct completer_data to the completion API Keith Seitz
2015-08-23 0:29 ` Doug Evans
2015-08-06 21:06 ` [PATCH v3 17/19] Make the completion API completely opaque Keith Seitz
2015-08-23 15:14 ` Doug Evans
2015-08-06 21:06 ` [PATCH v3 05/19] Implement completion limiting for ada_make_symbol_completion_list Keith Seitz
2015-08-23 3:47 ` Doug Evans
2015-08-06 22:03 ` [PATCH v3 13/19] Implement completion limiting for complete_on_enum Keith Seitz
2015-08-23 4:19 ` Doug Evans
2015-08-06 22:03 ` [PATCH v3 08/19] Implement completion limiting for signal_completer Keith Seitz
2015-08-23 3:59 ` Doug Evans
2015-08-06 22:03 ` [PATCH v3 11/19] Implement completion limiting for reg_or_group_completer Keith Seitz
2015-08-23 4:09 ` Doug Evans
2015-08-06 22:03 ` [PATCH v3 16/19] Implement completion limiting for tui_reggroup_completer Keith Seitz
2015-08-23 4:25 ` Doug Evans
2015-08-06 22:03 ` [PATCH v3 07/19] Implement completion limiting for filename_completer Keith Seitz
2015-08-23 3:58 ` Doug Evans
2015-08-06 22:12 ` [PATCH v3 10/19] Implement completion limiting for cmdpy_completer Keith Seitz
2015-08-23 4:07 ` Doug Evans
2015-08-06 22:12 ` [PATCH v3 14/19] Implement completion limiting in add_struct_fields Keith Seitz
2015-08-23 4:23 ` Doug Evans
2015-08-06 22:36 ` [PATCH v3 03/19] Implement completion-limiting for complete_on_cmdlist Keith Seitz
2015-08-23 1:05 ` Doug Evans
2015-08-07 2:37 ` [PATCH v3 15/19] Implement completion limiting for scmcmd_add_completion Keith Seitz
2015-08-23 4:24 ` Doug Evans
2015-08-07 22:57 ` [PATCH v3 00/19] New completer API Andrew Burgess
2015-08-08 0:04 ` Keith Seitz
2015-08-08 6:44 ` Andrew Burgess
2015-08-08 16:25 ` Keith Seitz
2015-08-22 22:25 ` 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=m37fomirvj.fsf@sspiff.org \
--to=xdje42@gmail.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