From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
linux-kernel@vger.kernel.org, 2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCH] perf-probe: fix perf-probe(1)'s report
Date: Sun, 26 Dec 2010 23:30:23 +0900 [thread overview]
Message-ID: <4D17517F.6060701@hitachi.com> (raw)
In-Reply-To: <m31v588r9k.fsf@gmail.com>
(2010/12/24 0:04), Franck Bui-Huu wrote:
> From: Franck Bui-Huu <fbuihuu@gmail.com>
>
> After adding probes, perf-probe(1) reports the probes locations which
> include filenames for certain cases.
>
> But for short file names (whose length < 32), perf-probe didn't display
> the name correctly. It actually skipped the first character.
>
> Here's an example where 'icmp.c' was screwed:
>
> $ perf probe -n -a "icmp.c;sk=*"
> Add new events:
> probe:icmp_push_reply (on @cmp.c)
> probe:icmp_reply (on @cmp.c)
> probe:icmp_reply_1 (on @cmp.c)
> probe:icmp_send (on @cmp.c)
> probe:icmp_send_1 (on @cmp.c)
> probe:icmp_error (on @cmp.c)
> probe:icmp_error_1 (on @cmp.c)
> probe:icmp_error_2 (on @cmp.c)
> probe:icmp_error_3 (on @cmp.c)
>
> This patch fixes this bug in synthesize_perf_probe_point().
Oops, I've missed that.
Thanks! that's really good catch!
Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
>
> Signed-off-by: Franck Bui-Huu <fbuihuu@gmail.com>
> ---
> tools/perf/util/probe-event.c | 16 ++++++++--------
> 1 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 10ad1ad..adc2620 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -1077,13 +1077,13 @@ static char *synthesize_perf_probe_point(struct perf_probe_point *pp)
> goto error;
> }
> if (pp->file) {
> - len = strlen(pp->file) - 31;
> - if (len < 0)
> - len = 0;
> - tmp = strchr(pp->file + len, '/');
> - if (!tmp)
> - tmp = pp->file + len;
> - ret = e_snprintf(file, 32, "@%s", tmp + 1);
> + tmp = pp->file;
> + len = strlen(tmp);
> + if (len > 30) {
> + tmp = strchr(pp->file + len - 30, '/');
> + tmp = tmp ? tmp + 1 : pp->file + len - 30;
> + }
> + ret = e_snprintf(file, 32, "@%s", tmp);
> if (ret <= 0)
> goto error;
> }
> @@ -1099,7 +1099,7 @@ static char *synthesize_perf_probe_point(struct perf_probe_point *pp)
>
> return buf;
> error:
> - pr_debug("Failed to synthesize perf probe point: %s",
> + pr_debug("Failed to synthesize perf probe point: %s\n",
> strerror(-ret));
> if (buf)
> free(buf);
--
Masami HIRAMATSU
2nd Dept. Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2010-12-26 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 15:04 [PATCH] perf-probe: fix perf-probe(1)'s report Franck Bui-Huu
2010-12-26 14:30 ` Masami Hiramatsu [this message]
2011-01-04 8:20 ` [tip:perf/core] perf probe: Fix short file name probe location reporting tip-bot for Franck Bui-Huu
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=4D17517F.6060701@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vagabon.xyz@gmail.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