From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] New field stop_pc in tracepoint_hit_ctx
Date: Fri, 02 Mar 2012 10:49:00 -0000 [thread overview]
Message-ID: <4F50A5B3.8040806@redhat.com> (raw)
In-Reply-To: <1330650011-31899-2-git-send-email-yao@codesourcery.com>
On 03/02/2012 01:00 AM, Yao Qi wrote:
> This patch is to add a new field `stop_pc' in tracepoint_hit_ctx, so
> parameter `stop_pc' used here and there can be removed. This change
> allows us to give a clean interface in next patch.
>
> Note the name `tracepoint_hit_ctx' is not very accurate, because it
> has been used in collect_data_at_step for "while-stepping" action also.
> It may be renamed to `tracepoint_action_ctx', which is about the
> context of doing tracepoint actions. I don't rename `tracepoint_hit_ctx'
> to keep this patch as readable as possible. I can send a follow-up
> patch to rename it if this change is reasonable.
>
> As `tracepoint_hit_ctx' is about the context of doing tracepoint
> actions, it is natural to add field `stop_pc' to show the pc value when
> to do tracepoint actions.
Fine with me, though honestly I find that the similarity between
tracepoint_action vs tracepoint_action_ctx will increase confusion,
not reduce.
> tpoint = ust_marker_to_static_tracepoint (mdata);
> + ctx.base.stop_pc = tpoint->address;
tpoint may be NULL, see just below.
> +
> if (tpoint == NULL)
> {
--
Pedro Alves
next prev parent reply other threads:[~2012-03-02 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 1:00 [patch 0/2] OO tracepoint_action Yao Qi
2012-03-02 1:00 ` [PATCH 1/2] New field stop_pc in tracepoint_hit_ctx Yao Qi
2012-03-02 10:49 ` Pedro Alves [this message]
2012-03-02 1:00 ` [PATCH 2/2] OO tracepoint_action Yao Qi
2012-03-02 1:06 ` Yao Qi
2012-03-02 11:50 ` Pedro Alves
2012-03-02 13:36 ` Yao Qi
2012-03-02 13:50 ` 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=4F50A5B3.8040806@redhat.com \
--to=palves@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