From: Michael Petlan <mpetlan@redhat.com>
To: "linux-perf-users@vger.kernel.org" <linux-perf-users@vger.kernel.org>
Subject: [PATCH] perf annotate: Support of full source file paths for srcline fix
Date: Mon, 09 Nov 2015 16:33:26 +0100 [thread overview]
Message-ID: <1447083206.15375.56.camel@Rudolf-RHEL-7> (raw)
Hi all,
the commit a9710ba091b0dcdace90f791706e9192313ffb7c has introduced
an option for showing basename/full path of the source files in the
perf report/script output. But regarding to perf annotate, the path
is always shown as basename, since the value of the related option
is not propagated into the annotating mechanism.
This patch addresses it and enables perf-annotate to print the full
paths as well.
Tested with latest git version.
Regards,
Michael
Michael Petlan (1):
perf annotate: Support of full source file paths for srcline fix
tools/perf/util/annotate.c | 1 +
1 file changed, 1 insertion(+)
--
1.8.3.1
next reply other threads:[~2015-11-09 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 15:33 Michael Petlan [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-09 15:33 [PATCH] perf annotate: Support of full source file paths for srcline fix Michael Petlan
2015-11-09 19:39 ` Arnaldo Carvalho de Melo
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=1447083206.15375.56.camel@Rudolf-RHEL-7 \
--to=mpetlan@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
/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