Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.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 03:39:00 -0000	[thread overview]
Message-ID: <52F5A67A.7010301@codesourcery.com> (raw)
In-Reply-To: <20140208031854.GM5485@adacore.com>

On 02/08/2014 11:18 AM, Joel Brobecker wrote:
> If we can allow a certain type of usage without damaging consequences
> for the rest of the operations, why not? Wouldn't it simplify the
> notification mechanism too?
> 

I am not familiar with the internals of FE, such as Eclipse, so hard to
tell change like this can break FE or not, but ...

> Food for thought:
> 
> I think it would be interesting to investigate whether FEs would
> notice if they started receiving those extra notifications. I hope
> the processing would be fast enough that they wouldn't.

... as you said, the investigation to FE should be useful to this
discussion.

> 
> 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.

-- 
Yao (齐尧)


  reply	other threads:[~2014-02-08  3:39 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 [this message]
2014-02-08 13:15             ` Joel Brobecker
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=52F5A67A.7010301@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=apoenitz@t-online.de \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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