From: Arun Sharma <asharma@fb.com>
To: Sam Liao <phyomh@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [BUG] perf report core dump
Date: Mon, 13 Jun 2011 13:16:59 -0700 [thread overview]
Message-ID: <4DF6703B.1040006@fb.com> (raw)
In-Reply-To: <BANLkTi=7uznMtmTFyu_UXgdV=WvS-eXq3g@mail.gmail.com>
On 6/11/11 9:24 AM, Sam Liao wrote:
> I noticed similar error, but It seems it leads by the "-s pid" option
> instead added "caller/callee" specifier. Remove this patch, symptom
> also showed up.
Yes - the bug doesn't seem to be caused by your patch, but it affects
the primary use case with -g graph,0.5,caller --sort pid.
builtin-report.c:
/*
* Only in the newt browser we are doing integrated annotation,
* so we don't allocated the extra space needed because the stdio
* code will not use it.
*/
if (al->sym != NULL && use_browser > 0) {
makes it clear why it hits the --tui case, but not --stdio. I'll
probably just disable this code path for now, until there is a better
solution.
-Arun
prev parent reply other threads:[~2011-06-13 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 23:15 [BUG] perf report core dump Arun Sharma
2011-06-11 16:24 ` Sam Liao
2011-06-13 20:16 ` Arun Sharma [this message]
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=4DF6703B.1040006@fb.com \
--to=asharma@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=phyomh@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;
as well as URLs for NNTP newsgroup(s).