From: Eli Zaretskii <eliz@gnu.org>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix PR14617: New MI notification on tracepoint modified.
Date: Tue, 30 Oct 2012 17:23:00 -0000 [thread overview]
Message-ID: <83vcdr7u2d.fsf@gnu.org> (raw)
In-Reply-To: <508F7BA3.3000005@codesourcery.com>
> Date: Tue, 30 Oct 2012 15:02:59 +0800
> From: Yao Qi <yao@codesourcery.com>
>
> On 10/18/2012 06:36 PM, Yao Qi wrote:
> > gdb:
> >
> > Fix PR gdb/14617.
> > * NEWS: Mention new MI notification "=tracepoint-modified".
> >
> > * breakpoint.c (trace_pass_set_count): Update caller of
> > observer_notify_tracepoint_modified.
> > * mi/mi-cmd-break.c (mi_cmd_break_passcount): Likewise.
> >
> > * mi/mi-interp.c: Declare 'mi_tracepoint_modified'.
> > (mi_interpreter_init): Attach 'mi_tracepoint_modified'
> > to 'tracepoint-modified' observer.
> > (mi_breakpoint_modified): New.
> > * observer.sh (struct objfile;): Declare 'struct tracepoint'.
> >
> > gdb/testsuite:
> >
> > Fix PR gdb/14617.
> > * gdb.mi/mi-breakpoint-changed.exp (test_insert_delete_modify):
> > Remove setup_kfail, and update test.
>
> Ping? http://sourceware.org/ml/gdb-patches/2012-10/msg00321.html
OK for the docs.
next prev parent reply other threads:[~2012-10-30 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:36 Yao Qi
2012-10-18 17:33 ` Eli Zaretskii
2012-10-30 7:03 ` Yao Qi
2012-10-30 17:23 ` Eli Zaretskii [this message]
2012-11-01 20:27 ` Tom Tromey
2012-11-02 6:38 ` Yao Qi
2012-11-02 14:42 ` Tom Tromey
2012-11-02 15:17 ` Pedro Alves
2012-11-02 15:22 ` Yao Qi
2012-11-02 15:25 ` Pedro Alves
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=83vcdr7u2d.fsf@gnu.org \
--to=eliz@gnu.org \
--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