From: Yao Qi <yao@codesourcery.com>
To: "Blanc, Nicolas" <nicolas.blanc@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Tom Tromey <tromey@redhat.com>, Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH 1/3] Added command remove-symbol-file.
Date: Fri, 26 Apr 2013 14:13:00 -0000 [thread overview]
Message-ID: <517A1A4C.6020207@codesourcery.com> (raw)
In-Reply-To: <388084C8C1E6A64FA36AD1D656E4856619DEF314@IRSMSX102.ger.corp.intel.com>
On 04/25/2013 08:48 PM, Blanc, Nicolas wrote:
> Tom> I liked Yao's comment about notifying just once per breakpoint. It doesn't seem difficult to do that.
> Nicolas> Ok I'll use a list of breakpoints to collect first the breakpoints to notify.
You may have a look at tracepoint.c:merge_uploaded_tracepoints, and see
how to notify once for one breakpoint. We use a vector 'modified_tp'
there to save the modified breakpoint uniquely, iterate over it, and
call observer_notify_breakpoint_modified. Hope it helps.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-04-26 6:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:22 [PATCH 0/3] remove-symbol-file Nicolas Blanc
2013-04-16 11:51 ` [PATCH 2/3] Test adding and removing a symbol file at runtime Nicolas Blanc
2013-04-24 12:18 ` Tom Tromey
2013-04-24 12:18 ` Tom Tromey
2013-04-16 12:18 ` [PATCH 1/3] Command remove-symbol-file Nicolas Blanc
2013-04-16 13:25 ` [PATCH 1/3] Added command remove-symbol-file Nicolas Blanc
2013-04-22 13:32 ` Yao Qi
2013-04-24 18:54 ` Tom Tromey
2013-04-25 19:24 ` Blanc, Nicolas
2013-04-25 20:07 ` Tom Tromey
2013-04-26 14:13 ` Yao Qi [this message]
2013-04-26 20:23 ` Pedro Alves
2013-04-30 7:30 ` Blanc, Nicolas
2013-04-30 9:28 ` Pedro Alves
2013-04-30 16:53 ` Blanc, Nicolas
2013-05-08 17:56 ` Pedro Alves
2013-05-28 11:25 ` Blanc, Nicolas
2013-04-16 14:18 ` [PATCH 3/3] Documentation for the remove-symbol-file command Nicolas Blanc
2013-04-16 15:12 ` Eli Zaretskii
2013-04-24 9:22 ` [PATCH 0/3] remove-symbol-file Tom Tromey
2013-04-24 20:40 ` Blanc, Nicolas
2013-04-24 20:49 ` Pedro Alves
2013-04-25 17:25 ` Blanc, Nicolas
2013-04-26 19:13 ` Pedro Alves
2013-04-24 17:46 ` 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=517A1A4C.6020207@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=nicolas.blanc@intel.com \
--cc=palves@redhat.com \
--cc=tromey@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