From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Allow to enable run/stop notifications for function calls.
Date: Fri, 02 May 2008 16:21:00 -0000 [thread overview]
Message-ID: <200805022002.56292.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080502155907.GU29202@caradoc.them.org>
On Friday 02 May 2008 19:59:07 Daniel Jacobowitz wrote:
> On Thu, May 01, 2008 at 05:51:48PM +0400, Vladimir Prus wrote:
> >
> > I've already posted patches to produce more accurate *stopped notifications
> > in MI and introduce *running notification. Those notification are not produced
> > during inferior function calls, as it's very likely than an unprepared frontend
> > will try to refetch everything in response to those *stopped, re-evaluating all
> > expression again, calling functions again, etc.
> >
> > This patch allows a frontend to request the notification for function
> > calls to be still emitted, by using
> >
> > -enable-feature infcall-run-stop-notifications
> >
> > OK?
>
> 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?
> 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.
- Volodya
next prev parent reply other threads:[~2008-05-02 16:03 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 [this message]
2008-05-02 16:55 ` 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=200805022002.56292.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=drow@false.org \
--cc=gdb-patches@sources.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