Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Matt Rice <ratmice@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch/rfc] mi interpreter-complete enh req 8058.
Date: Fri, 02 Oct 2009 20:55:00 -0000	[thread overview]
Message-ID: <m3r5tlo6s1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8ba6bed40910021037q16276bb7w83ec3a5f20e2cbd1@mail.gmail.com> 	(Matt Rice's message of "Fri, 2 Oct 2009 10:37:14 -0700")

>>>>> "Matt" == Matt Rice <ratmice@gmail.com> writes:

Matt> Attached is a patch i've ported from Apple's gdb...
Matt> it implements a tab-completion like function for MI
Matt> http://sourceware.org/bugzilla/show_bug.cgi?id=8058
Matt> I figured I would post a basic port of the patch for discussion,
Matt> before doing to much to it.

Thanks.

Matt> it only implements complete_proc for the console interpreter, why
Matt> then 'interpreter-complete' if only the console interpreter
Matt> implements it?

I have no idea.

Matt> it has arbitrary limits of 200 completions which has never really been
Matt> a part of the gnu credo:
Matt> one idea is to introduce a limit argument to the mi command, but that
Matt> brings up the idea of bringing in a starting point for resuming
Matt> completion, and getting multiple batches

Matt> without some form of a continuation it'd have to redo the
Matt> completion each batch, it seems difficult/impossible to invalidate
Matt> the completion e.g. if loading/completing symbols

Matt> so maybe we should forgo the batching but add the limit to the mi command?

Yeah, some solution here would be nice to have.
This is related to http://sourceware.org/bugzilla/show_bug.cgi?id=9007

I suppose some kind of continuation is not out of the question.

Matt> I also notice it doesn't implement the all? argument that he mentioned
Matt> in the bug report.

If you don't need that, you can ignore it, IMO.

Matt> also need to add a  -list-features thing...

I think it is probably fine not to do that and just let clients catch
the error coming from older GDBs.

Matt> adding arguments and things obviously would break compatibility with
Matt> their gdb, is this an issue?

IMO, it is not an issue.  But, if it is easy to be compatible, we might
as well be.

Matt> -interpreter-complete console "b ma"
Matt> ^done,completions=[c="main",c="malloc",c="malloc@plt"]

It is weird to see all those useless "c=" strings in there :-)

The patch seems reasonable enough.  There are some GNU style issues to
clean up.  And, this would need an update to the manual.

Tom


  reply	other threads:[~2009-10-02 20:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 17:37 Matt Rice
2009-10-02 20:55 ` Tom Tromey [this message]
2009-10-02 23:10   ` Nick Roberts
2009-10-03 19:00     ` Matt Rice
2009-10-04  0:12       ` Nick Roberts
2009-10-05  8:00         ` Matt Rice

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=m3r5tlo6s1.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ratmice@gmail.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