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: Thu, 18 Oct 2012 17:33:00 -0000 [thread overview]
Message-ID: <83mwzj1y83.fsf@gnu.org> (raw)
In-Reply-To: <1350556586-12800-1-git-send-email-yao@codesourcery.com>
> From: Yao Qi <yao@codesourcery.com>
> Date: Thu, 18 Oct 2012 18:36:26 +0800
>
> As PR gdb/14617 described, when the passcount of a tracepoint is
> modified, GDB doesn't emit any notification. This patch adds a
> new notification '=tracepoint-modified' for the changes to
> tracepoint-specific attributes. The reason I don't use
> '=breakpoint-modified' notification is that IMO, it is about
> changes to general breakpoints (breakpoint, tracepoint, catchpoint,
> etc), so I don't want to put tracepoint-specific stuff into
> it.
>
> Regression tested on x86_64-linux with both native and gdbserver,
> OK to apply?
The documentation parts are OK. Thanks.
next prev parent reply other threads:[~2012-10-18 17:33 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 [this message]
2012-10-30 7:03 ` Yao Qi
2012-10-30 17:23 ` Eli Zaretskii
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=83mwzj1y83.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