From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Allow to enable run/stop notifications for function calls.
Date: Fri, 02 May 2008 16:55:00 -0000 [thread overview]
Message-ID: <20080502162100.GA7412@caradoc.them.org> (raw)
In-Reply-To: <200805022002.56292.vladimir@codesourcery.com>
On Fri, May 02, 2008 at 08:02:55PM +0400, Vladimir Prus wrote:
> > I'm still not convinced we need -enable-feature for anything that
> > -gdb-set and -gdb-show can not handle.
>
> Is -gdb-show output specified in any way? Is it subject to i18n?
Good point. For settings we expect MI clients to be interested in,
we could use the ui_out mechanism to give them named fields. I think
that will work fine.
> > What do you think about bundling this sort of update into MI version
> > 3? That cuts down on the number of possible knobs for output, which
> > is IMO important.
>
> Well, this might be good idea, provided everybody concerned agree that
> MI3 will be rapidly changing until futher notice and *no* compatibility
> will be guaranteed until that point.
I think that's fine, if we think we can settle it down by the next
release. Or the first release to fully support non-stop and async,
if that's not in time for the next release. At some point we will
have to lock it in place, like we did for mi2.
Existing clients should be using mi2. Some are probably just using
-i=mi, but that's an easy bug to fix.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-05-02 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 13:52 Vladimir Prus
2008-05-02 9:58 ` Eli Zaretskii
2008-05-02 16:02 ` Daniel Jacobowitz
2008-05-02 16:21 ` Vladimir Prus
2008-05-02 16:55 ` Daniel Jacobowitz [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=20080502162100.GA7412@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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