From: Nick Roberts <nickrob@snap.net.nz>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Eli Zaretskii <eliz@gnu.org>,
drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [mi] -list-features
Date: Fri, 31 Aug 2007 07:27:00 -0000 [thread overview]
Message-ID: <18135.49879.287098.143052@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200708311105.38612.ghost@cs.msu.su>
> How about this:
>
> -list-features Returns a list of particular features of the MI
> protocol that this version of gdb implements. A feature can
> be a command, or a new field in an output of some command,
> or even an important bugfix. While a frontend can sometimes
> detect presence of a feature at runtime, it is easier to
> perform detection at debugger startup.
>
> The command returns a list of strings, with each string naming
> an available feature. Each returned string is just a name, it
> does not have any internal structure. The list of possible
> feature names is given below.
>
> The current list of features is:
>
> - 'frozen-varobjs' -- indicates presence of -var-set-frozen
> command, as well as possible presense of the 'frozen' field
> in the output of -varobj-create.
You've lost me. This is plain text documentation for a command which you
want to implement now but populate later. Something like:
(gdb)
-list-features
^done,features=[]
AFAICS it won't currently return 'frozen-varobjs. Since everyone seems
agreeable to the general idea why not just submit when the patch (source and
documentation) are complete?
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-08-31 7:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 17:12 Vladimir Prus
2007-08-28 17:15 ` Daniel Jacobowitz
2007-08-28 17:47 ` Vladimir Prus
2007-08-29 17:55 ` Eli Zaretskii
2007-08-31 7:06 ` Vladimir Prus
2007-08-31 7:27 ` Nick Roberts [this message]
2007-08-31 7:38 ` Vladimir Prus
2007-08-31 9:00 ` Nick Roberts
2007-08-31 8:50 ` Eli Zaretskii
2007-08-31 9:00 ` Vladimir Prus
2007-08-31 9:18 ` Eli Zaretskii
2007-08-31 9:33 ` Nick Roberts
2007-08-31 9:44 ` Vladimir Prus
2007-08-31 10:02 ` Nick Roberts
2007-08-31 10:13 ` Vladimir Prus
2007-08-31 20:12 ` Nick Roberts
2007-08-31 10:19 ` Vladimir Prus
2007-08-31 18:08 ` Eli Zaretskii
2007-09-07 20:26 ` Vladimir Prus
2007-09-08 7:24 ` Eli Zaretskii
2007-09-16 14:23 ` Vladimir Prus
2007-09-16 14:38 ` Daniel Jacobowitz
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=18135.49879.287098.143052@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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