From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [RCF 0/6 V2] MI notification of command option change
Date: Fri, 27 Jul 2012 14:15:00 -0000 [thread overview]
Message-ID: <4000941.imkHvyQvi6@qiyao.dyndns.org> (raw)
In-Reply-To: <1343397901-15051-1-git-send-email-yao@codesourcery.com>
On Friday, July 27, 2012 10:04:54 PM Yao Qi wrote:
> 1. Kee the command-registration functions unchanged (discard
> my xxx_wit_notif functions).
> 2. Don't emit option change of *all* gdb commands. We have to
> set 'reporting' commands via function 'set_cmd_notify', otherwise
> commands are still 'no-reporting'. I believe that frontends will
> request more and more options changes, but changes of some gdb
> options are useless to frontends. It is noisy to send all option
> changes.
>
> Tom and Pedro's review comments are addressed in this version.
I just missed Pedro's comment on 'using array reduces the debugability of
gdb'. I'll fix that. Please ignore this thread. Sorry for the noise here.
--
Yao (齐尧)
next prev parent reply other threads:[~2012-07-27 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 14:06 Yao Qi
2012-07-27 14:06 ` [PATCH 1/7] new observer command_option_changed Yao Qi
2012-07-27 14:06 ` [PATCH 2/7] allow to suppress more mi notification Yao Qi
2012-07-27 14:06 ` [PATCH 4/7] notify in enum_cmd and scheduler-locking Yao Qi
2012-07-27 14:07 ` [PATCH 3/7] attach to command_option-changed observer Yao Qi
2012-07-27 18:07 ` Eli Zaretskii
2012-07-27 14:07 ` [PATCH 6/7] notify in string_cmd and trace-notes Yao Qi
2012-07-27 14:07 ` [PATCH 7/7] code indentation Yao Qi
2012-07-27 14:07 ` [PATCH 5/7] notify in boolean_cmd and circular-trace-buffer Yao Qi
2012-07-27 14:15 ` Yao Qi [this message]
2012-07-27 15:23 [RCF 0/6 V2] MI notification of command option change Yao Qi
2012-07-27 17:07 ` Tom Tromey
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=4000941.imkHvyQvi6@qiyao.dyndns.org \
--to=yao@codesourcery.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