From: Pedro Alves <pedro@palves.net>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Simon Marchi <simark@simark.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: improve command completion for 'print', 'x', and 'display'
Date: Fri, 8 Jan 2021 15:08:00 +0000 [thread overview]
Message-ID: <05d3b626-3933-80fc-2bc6-ea17d8d3ae32@palves.net> (raw)
In-Reply-To: <20210108103452.GX2945@embecosm.com>
On 08/01/21 10:34, Andrew Burgess wrote:
> * Pedro Alves <pedro@palves.net> [2021-01-08 00:59:25 +0000]:
>
>> On 27/11/20 11:13, Andrew Burgess wrote:
>>> Previously when analysing /FMT strings for tab completion we
>>> considered two possibilities, either the user has typed '/', or the
>>> user has typed '/' followed by an alpha-numeric character, as these
>>> are the only valid FMT string characters.
>>>
>>> This meant that if the user type, for example '/@' and then tried to
>>> tab complete gdb would use an uninitialised variable.
>>>
>>> Currently only the first character after the '/' is checked to see if
>>> it is alpha-numeric, so if a user typed '/x@@' then gdb would be happy
>>> to treat this as a FMT string.
>>>
>>> Given the goal of this change was primarily to allow tab completion of
>>> symbols later in the command when a /FMT was used then I decided to
>>> just make the /FMT skipping less smart. Now any characters after the
>>> '/' up to the first white space, will be treated as a FMT string.
>>
>> Do we already have a test for this?
>
> No. My bad.
>
> How about the below?
LGTM, thanks!
prev parent reply other threads:[~2021-01-08 15:08 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 ` [PATCH] gdb: improve command completion for 'print', 'x', and 'display' Simon Marchi
2020-11-27 11:13 ` 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 [this message]
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=05d3b626-3933-80fc-2bc6-ea17d8d3ae32@palves.net \
--to=pedro@palves.net \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).