From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <yao@codesourcery.com>
Cc: andre <apoenitz@t-online.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Test no =breakpoint-modified is emitted for modifications from MI commands
Date: Sat, 08 Feb 2014 13:15:00 -0000 [thread overview]
Message-ID: <20140208131533.GN5485@adacore.com> (raw)
In-Reply-To: <52F5A67A.7010301@codesourcery.com>
> > One other possible option: Add a new option that would be available
> > to all commands to disable notifications related to the command being
> > executed. That way, FE could use it to reduce unnecessary back-chatter.
>
> That is what I am thinking about.
>
> > I don't really like that option, though, as it would require a certain
> > transition period.
>
> What do you mean by "transition period"? We can make use of
> "-list-features" to tell FE that FE can disable/enable MI notifications
> through a certain command.
The issue is people using older versions of an FE with a newer version
of GDB. For those, their FE wouldn't know about the new option and
thus get the notifications that they might not expect.
I don't know if we need to be concerned about this sort of compatibility
or not...
--
Joel
next prev parent reply other threads:[~2014-02-08 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 7:48 Yao Qi
2014-02-06 12:38 ` Yao Qi
2014-02-06 20:39 ` andre
2014-02-07 9:14 ` Yao Qi
2014-02-07 16:12 ` andre
2014-02-08 3:18 ` Joel Brobecker
2014-02-08 3:39 ` Yao Qi
2014-02-08 13:15 ` Joel Brobecker [this message]
2014-02-08 14:11 ` andre
2014-02-07 14:04 ` Pedro Alves
2014-02-08 1:49 ` Yao Qi
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=20140208131533.GN5485@adacore.com \
--to=brobecker@adacore.com \
--cc=apoenitz@t-online.de \
--cc=gdb-patches@sourceware.org \
--cc=yao@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