From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RCF 0/6 V2] MI notification of command option change
Date: Fri, 27 Jul 2012 17:07:00 -0000 [thread overview]
Message-ID: <876299cevh.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1343402543-665-1-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 27 Jul 2012 23:22:17 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> 2. Don't emit option change of all gdb commands. We have to
Yao> set 'reporting' commands via function 'set_cmd_notify', otherwise
Yao> commands are still 'no-reporting'. I believe that frontends will
Yao> request more and more options changes, but changes of some gdb
Yao> options are useless to frontends. It is noisy to send all option
Yao> changes.
Yesterday's discussions convinced me that the best route is to report
all changes.
If it is really necessary to throttle changes, then I think there should
be a new MI command so that the MI client can specify which ones it does
or does not want to see.
Tom
next prev parent reply other threads:[~2012-07-27 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:23 Yao Qi
2012-07-27 15:23 ` [PATCH 3/6] notify in enum_cmd and scheduler-locking Yao Qi
2012-07-27 15:23 ` [PATCH 6/6] code indentation Yao Qi
2012-07-27 15:23 ` [PATCH 2/6] attach to command_option-changed observer Yao Qi
2012-07-27 17:20 ` Tom Tromey
2012-07-27 17:44 ` Tom Tromey
2012-07-27 15:23 ` [PATCH 1/6] new observer command_option_changed Yao Qi
2012-07-27 17:56 ` Tom Tromey
2012-07-27 15:23 ` [PATCH 5/6] notify in string_cmd and trace-notes Yao Qi
2012-07-27 15:23 ` [PATCH 4/6] notify in boolean_cmd and circular-trace-buffer Yao Qi
2012-07-27 17:07 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-27 14:06 [RCF 0/6 V2] MI notification of command option change Yao Qi
2012-07-27 14:15 ` 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=876299cevh.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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