Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix PR14617: New MI notification on tracepoint modified.
Date: Fri, 02 Nov 2012 15:22:00 -0000	[thread overview]
Message-ID: <5093E50F.2050604@codesourcery.com> (raw)
In-Reply-To: <5093E3EF.6080903@redhat.com>

On 11/02/2012 11:17 PM, Pedro Alves wrote:
> For all of this, I'm against this new notification.  Just make changing
> the tracepoint emit the existing =breakpoint-modified notification.
> Why doesn't that work?

Pedro, I realized this issue during patch review.  I posted a new one 
which uses 'breakpoint-modified' notification for tracepoint as well.

   http://sourceware.org/ml/gdb-patches/2012-11/msg00033.html

-- 
Yao


  reply	other threads:[~2012-11-02 15:22 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
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 [this message]
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=5093E50F.2050604@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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