From: Simon Marchi <simark@simark.ca>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: improve command completion for 'print', 'x', and 'display'
Date: Thu, 26 Nov 2020 14:12:34 -0500 [thread overview]
Message-ID: <05be3103-96e3-6e2d-902a-a1e35a166389@simark.ca> (raw)
In-Reply-To: <20201116154221.240877-1-andrew.burgess@embecosm.com>
On 2020-11-16 10:42 a.m., Andrew Burgess wrote:
> The /FMT specification on the print command currently breaks command
> completion, so:
>
> (gdb) p var.<TAB><TAB>
> .... list of fields in var .....
>
> But,
>
> (gdb) p/d var.<TAB><TAB>
> ..... list of all symbols .....
>
> After this commit this issue is now resolved.
>
> There are some other details around tab-completion and /FMT which
> hopefully this commit improves. So, before:
>
> (gdb) p/<TAB><TAB>
> .... lists all symbols .....
>
> After:
>
> (gdb) p/<TAB><TAB> # Nothing changes...
>
> The thinking here is that after a / the user must type a FMT, but we
> don't offer tab completion on FMT characters. Placing a symbol
> directly after a / will not do what the user expects, so offering that
> seems wrong.
>
> Similarly, before we had:
>
> (gdb) p/d<TAB><TAB>
> ... lists all symbols starting with 'd' ....
>
> But afterwards:
>
> (gdb) p/d<TAB><TAB> # Adds a single space, so we get:
> (gdb) p/d <CURSOR>
>
> As before, typing a symbol where FMT is expected will not do what the
> user expects. If the user has added a FMT string then upon tab
> completion GDB assumes the FMT string is complete and prepares the
> user to type an expression.
>
> In this commit I have also added completion functions for the 'x' and
> 'display' commands. These commands also support /FMT specifiers and
> so share some code with 'print'.
>
> gdb/ChangeLog:
>
> * printcmd.c: Include 'safe-ctype.c'.
> (skip_over_slash_fmt): New function.
> (print_command_completer): Call skip_over_slash_fmt.
> (display_and_x_command_completer): New function.
> (_initialize_printcmd): Add command completion for 'x' and
> 'display'.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.base/completion.exp: Add new tests.
> ---
> gdb/ChangeLog | 9 +++
> gdb/printcmd.c | 81 ++++++++++++++++++++++++++-
> gdb/testsuite/ChangeLog | 4 ++
> gdb/testsuite/gdb.base/completion.exp | 26 +++++++++
> 4 files changed, 118 insertions(+), 2 deletions(-)
I noticed this warning in the code added by this patch, I think it's not a false positive:
/home/simark/src/binutils-gdb/gdb/printcmd.c: In function ‘bool skip_over_slash_fmt(completion_tracker&, const char**)’:
/home/simark/src/binutils-gdb/gdb/printcmd.c:1285:14: warning: ‘in_fmt’ may be used uninitialized in this function [-Wmaybe-uninitialized]
1285 | return in_fmt;
| ^~~~~~
Simon
next prev parent reply other threads:[~2020-11-26 19:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:42 Andrew Burgess
2020-11-16 23:53 ` Pedro Alves
2020-11-18 16:11 ` Tom Tromey
2020-11-19 10:14 ` Andrew Burgess
2020-11-20 13:47 ` Pedro Alves
2020-11-20 15:55 ` Tom Tromey
2020-11-21 10:42 ` Andrew Burgess
2020-12-03 17:03 ` Tom Tromey
2020-12-11 22:07 ` Andrew Burgess
2021-01-06 7:39 ` gdbserver build broken with -fsanitize=address Tom de Vries
2021-01-06 16:29 ` [PATCH][gdb/build] Fix gdbserver build " Tom de Vries
2021-01-07 9:24 ` Andrew Burgess
2020-11-26 19:12 ` Simon Marchi [this message]
2020-11-27 11:13 ` [PATCH] gdb: improve command completion for 'print', 'x', and 'display' Andrew Burgess
2020-11-27 14:04 ` Simon Marchi
2021-01-08 0:59 ` Pedro Alves
2021-01-08 10:34 ` Andrew Burgess
2021-01-08 15:08 ` 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=05be3103-96e3-6e2d-902a-a1e35a166389@simark.ca \
--to=simark@simark.ca \
--cc=andrew.burgess@embecosm.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).