From: Andi Kleen <ak@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
acme@redhat.com, mingo@kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, namhyung@kernel.org
Subject: Re: [PATCH 2/8] perf, tools: Support handling complete branch stacks as histograms v4
Date: Wed, 5 Mar 2014 07:31:49 -0800 [thread overview]
Message-ID: <20140305153149.GQ12219@tassilo.jf.intel.com> (raw)
In-Reply-To: <20140305102948.GB1835@krava.brq.redhat.com>
> segfaults here..
>
> [jolsa@krava perf]$ ./perf record -g sleep 1
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.013 MB perf.data (~567 samples) ]
> [jolsa@krava perf]$ ./perf report
> perf: Segmentation fault
> [jolsa@krava perf]$
Thanks. Fixed with this patch:
commit 124014960a8fb09043914fb79ea86e0444408ab0
Author: Andi Kleen <ak@linux.intel.com>
Date: Wed Mar 5 07:28:56 2014 -0800
perf, tools, report: Fix perf report without -b
Fix report crash when -b is not used. Reported by Jiri Olsa.
Signed-off-by: Andi Kleen <ak@linux.intel.com>
diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
index ef198c3..04ec451 100644
--- a/tools/perf/util/machine.c
+++ b/tools/perf/util/machine.c
@@ -1381,15 +1381,15 @@ static int machine__resolve_callchain_sample(struct machine *machine,
* - No annotations (should annotate somehow)
*/
- if (branch->nr > PERF_MAX_BRANCH_DEPTH) {
- pr_warning("corrupted branch chain. skipping...\n");
- return 0;
- }
-
- if (callchain_param.branch_callstack) {
+ if (branch && callchain_param.branch_callstack) {
int nr = min(max_stack, (int)branch->nr);
struct branch_entry be[nr];
+ if (branch->nr > PERF_MAX_BRANCH_DEPTH) {
+ pr_warning("corrupted branch chain. skipping...\n");
+ return 0;
+ }
+
for (i = 0; i < nr; i++) {
if (callchain_param.order == ORDER_CALLEE) {
be[i] = branch->entries[i];
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2014-03-05 15:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 4:22 perf: Implement lbr-as-callgraph v4 Andi Kleen
2014-02-28 4:22 ` [PATCH 1/8] perf, tools: fix BFD detection on opensuse Andi Kleen
2014-02-28 4:22 ` [PATCH 2/8] perf, tools: Support handling complete branch stacks as histograms v4 Andi Kleen
2014-03-05 10:29 ` Jiri Olsa
2014-03-05 15:31 ` Andi Kleen [this message]
2014-03-07 13:19 ` Jiri Olsa
2014-03-07 13:19 ` Jiri Olsa
2014-03-07 19:51 ` Arnaldo Carvalho de Melo
2014-03-07 19:54 ` Arnaldo Carvalho de Melo
2014-03-11 0:43 ` Andi Kleen
2014-02-28 4:22 ` [PATCH 3/8] perf, tools: Add --branch-history option to report v2 Andi Kleen
2014-03-07 13:19 ` Jiri Olsa
2014-03-11 0:31 ` Andi Kleen
2014-03-11 15:25 ` Jiri Olsa
2014-03-11 20:21 ` Andi Kleen
2014-02-28 4:22 ` [PATCH 4/8] perf, tools: Enable printing the srcline in the history v2 Andi Kleen
2014-03-01 16:22 ` Andi Kleen
2014-02-28 4:22 ` [PATCH 5/8] perf, tools: Only print base source file for srcline Andi Kleen
2014-02-28 4:22 ` [PATCH 6/8] perf, tools: Support source line numbers in annotate Andi Kleen
2014-02-28 4:22 ` [PATCH 7/8] perf, tools: Fix srcline sort key output to use width Andi Kleen
2014-02-28 4:22 ` [PATCH 8/8] tools, perf: Make get_srcline fall back to sym+offset Andi Kleen
2014-03-07 13:19 ` Jiri Olsa
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=20140305153149.GQ12219@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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