From: Jiri Olsa <jolsa@redhat.com>
To: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
Cc: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"jolsa@kernel.org" <jolsa@kernel.org>
Subject: Re: perf report: null ptr dereference in utils/env.c
Date: Wed, 19 Oct 2016 11:11:56 +0200 [thread overview]
Message-ID: <20161019091156.GA13603@krava> (raw)
In-Reply-To: <D6EDEBF1F91015459DB866AC4EE162CC02499E90@IRSMSX103.ger.corp.intel.com>
On Wed, Oct 19, 2016 at 08:29:41AM +0000, Odzioba, Lukasz wrote:
> On Wednesday, October 19, 2016 12:04 AM, Jiri Olsa wrote:
> > could you please try with Arnaldo's current perf/urgent branch
> > that has following patch:
> > f957a5308dbb perf header: Set nr_numa_nodes only when we parsed all the data
> >
> > is that ppc machine? how did you generate the perf.data?
>
> It does make the problem go away.
>
> x86_64, generated by:
> # perf record -- ls
> # perf report
hum, I still can't reproduce this.. could you please send
me your kernel's config file?
thanks,
jirka
prev parent reply other threads:[~2016-10-19 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 16:13 perf report: null ptr dereference in utils/env.c Odzioba, Lukasz
2016-10-18 22:04 ` Jiri Olsa
2016-10-19 8:29 ` Odzioba, Lukasz
2016-10-19 9:11 ` Jiri Olsa [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=20161019091156.GA13603@krava \
--to=jolsa@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lukasz.odzioba@intel.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).