From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/3] attach to command_param_changed observer.
Date: Fri, 03 Aug 2012 17:36:00 -0000 [thread overview]
Message-ID: <87vcgznajc.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1343992904-9375-3-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Fri, 3 Aug 2012 19:21:43 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> 2012-08-03 Yao Qi <yao@codesourcery.com>
Yao> * NEWS: Mention new MI notification.
Yao> * mi/mi-interp.c: Declare mi_command_param_changed.
Yao> (mi_interpreter_init): Attach mi_command_param_changed to
Yao> observer command_param_changed.
Yao> (mi_command_param_changed): New.
Yao> Remove mi_suppress_breakpoint_notifications.
Yao> Define global variable mi_suppress_notification.
Yao> (mi_breakpoint_created): Update.
Yao> (mi_breakpoint_deleted): Likewise.
Yao> (mi_breakpoint_modified): Likewise.
Yao> * mi/mi-main.c (mi_cmd_execute): Likewise. Check command
Yao> 'gdb-set' and set mi_suppress_notification.
Yao> * mi/mi-main.h: (mi_suppress_notification): New struct.
Code bits are ok once patch #1 is resolved.
Tom
next prev parent reply other threads:[~2012-08-03 17:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 11:22 [RCF 0/3 V3] MI notification of command parameter change Yao Qi
2012-08-03 11:22 ` [PATCH 3/3] test case Yao Qi
2012-08-03 17:37 ` Tom Tromey
2012-08-06 15:48 ` Yao Qi
2012-08-06 20:21 ` Tom Tromey
2012-08-03 11:22 ` [PATCH 1/3] new observer command_param_changed Yao Qi
2012-08-03 17:35 ` Tom Tromey
2012-08-06 15:44 ` Yao Qi
2012-08-06 20:21 ` Tom Tromey
2012-08-07 2:58 ` Yao Qi
2012-08-08 18:11 ` Tom Tromey
2012-08-03 11:22 ` [PATCH 2/3] attach to command_param_changed observer Yao Qi
2012-08-03 11:30 ` Eli Zaretskii
2012-08-03 17:36 ` Tom Tromey [this message]
2012-08-10 0:57 ` [committed]: [RCF 0/3 V3] MI notification of command parameter change 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=87vcgznajc.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