From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [mi] -list-features
Date: Wed, 29 Aug 2007 17:55:00 -0000 [thread overview]
Message-ID: <ur6lmb4z3.fsf@gnu.org> (raw)
In-Reply-To: <200708282147.18298.ghost@cs.msu.su> (message from Vladimir Prus on Tue, 28 Aug 2007 21:47:17 +0400)
> From: Vladimir Prus <ghost@cs.msu.su>
> Date: Tue, 28 Aug 2007 21:47:17 +0400
> Cc: gdb-patches@sources.redhat.com
>
> -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 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.
> .........
This is fine, but for it to be useful to front ends, I think you need
to tell more about the format of the output, because a program will
need to parse and understand it. Let's say I want to test for the
support of a feature name "frobnicate", how would I go about it?
TIA
next prev parent reply other threads:[~2007-08-29 17:55 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 [this message]
2007-08-31 7:06 ` Vladimir Prus
2007-08-31 7:27 ` Nick Roberts
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=ur6lmb4z3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.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