From: Daniel Gutson <daniel.gutson@tallertechnologies.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add autocompletion for convenience vars in print and set
Date: Tue, 27 May 2014 15:18:00 -0000 [thread overview]
Message-ID: <CAF5HaEVHquyaanGLQTHc9RAWdUsNoggM-qJpiwU76xSzbgF8fg@mail.gmail.com> (raw)
In-Reply-To: <CAF5HaEUosXVSvxJQkEp3DgBYMMKGNXnJ-r4LOQV3PDeqfYnptA@mail.gmail.com>
ping for maintainer.
Thanks.
On Thu, May 22, 2014 at 12:17 PM, Daniel Gutson
<daniel.gutson@tallertechnologies.com> wrote:
> Second version.
> Comments below:
>
> On Tue, May 20, 2014 at 1:36 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>>> "Daniel" == Daniel Gutson <daniel.gutson@tallertechnologies.com> writes:
>>
>> Daniel> I could not find any testsuite where to add tests for this; if
>> Daniel> there are, please let me know.
>>
>> See testsuite/gdb.base/completion.exp
>
> Thanks, I ran all the tests and passed. I did not add a new test
> case though since I didn't check how to add a new convenience var
> and undefine it later from the test framework. (Should I try harder?)
>
>>
>> Daniel> exp : VARIABLE
>> Daniel> {
>> Daniel> - write_dollar_variable (pstate, $1);
>> Daniel> + if (!parse_completion)
>> Daniel> + write_dollar_variable (pstate, $1);
>> Daniel> }
>>
>> I think this isn't correct. I think it won't work if you try to
>> complete on a field name where the "LHS" has a convenience variable.
>> That is something like:
>>
>> set $var = (struct x *) malloc (...)
>> complete print $var.somethin
>
> You were right, that was broken.
>
>>
>> Instead I think you need a new production, like "exp : VARIABLE COMPLETE".
>
> I found another solution without touching the yacc file: adding a check
> inside write_dollar_variable
>
>>
>> Daniel> + if (p != NULL && *p == '$')
>> Daniel> + return complete_internalvar (p + 1);
>>
>> I'm not sure this is correct either, but offhand I don't know.
>> Should it not look at "word"?
>
> It actually works ("word" didn't have the $).
>
> However, I noticed that 'set' cmd autocomplete doesn't work for
> members of structures (neither with convenience vars nor regular
> symbols). I'll address that in the next patch once this gets approved
> and committed.
>
>>
>> Daniel> + VEC (char_ptr) * ret = current_language->la_make_symbol_completion_list (
>> Daniel> + text, word,
>> Daniel> + TYPE_CODE_UNDEF);
>>
>> No space before "ret".
>> The line breaks look odd, I would break before the "=" and not after the "(".
>>
>> thanks,
>> Tom
>
> 2014-05-22 Daniel Gutson <daniel.gutson@tallertechnologies.com>
>
> gdb/
> * parse.c (write_dollar_variable): Do not create an internal
> var when completing.
> * completer.c (expression_completer): Call complete_internalvar.
> * symtab.c (make_symbol_completion_list): Call complete_internalvar.
--
Daniel F. Gutson
Chief Engineering Officer, SPD
San Lorenzo 47, 3rd Floor, Office 5
Córdoba, Argentina
Phone: +54 351 4217888 / +54 351 4218211
Skype: dgutson
next prev parent reply other threads:[~2014-05-27 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 15:51 Daniel Gutson
2014-05-20 15:52 ` Daniel Gutson
2014-05-20 16:36 ` Tom Tromey
2014-05-22 15:17 ` Daniel Gutson
2014-05-27 15:18 ` Daniel Gutson [this message]
2014-05-27 16:46 ` Andrew Burgess
2014-05-27 20:24 ` Daniel Gutson
2016-02-25 21:23 ` Daniel Gutson
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=CAF5HaEVHquyaanGLQTHc9RAWdUsNoggM-qJpiwU76xSzbgF8fg@mail.gmail.com \
--to=daniel.gutson@tallertechnologies.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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