linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 00:04:08 +0200	[thread overview]
Message-ID: <20161018220408.GA3286@krava> (raw)
In-Reply-To: <D6EDEBF1F91015459DB866AC4EE162CC02499B19@IRSMSX103.ger.corp.intel.com>

On Tue, Oct 18, 2016 at 04:13:45PM +0000, Odzioba, Lukasz wrote:
> Hi,
> Am I the only one getting segfaults in perf report (4.8-rc8/4.9rc-1)?
> It happens simply when I try to exit it.
> 
> Program received signal SIGSEGV, Segmentation fault.
> perf_env__exit (env=env@entry=0x1fc4d00) at util/env.c:25
> (...)
> (gdb) list
> (...)
> 
> 24              for (i = 0; i < env->nr_numa_nodes; i++)
> 25                      cpu_map__put(env->numa_nodes[i].map);
> 26              zfree(&env->numa_nodes);
>  
>  (gdb) print env->nr_numa_nodes
> $1 = 2
>  (gdb) print env->numa_nodes
> $2 = (struct numa_node *) 0x0    
> 
> This line was introduced in the following patch:
> https://patchwork.kernel.org/patch/9213995/

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?

thanks,
jirka

  reply	other threads:[~2016-10-18 22:04 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 [this message]
2016-10-19  8:29   ` Odzioba, Lukasz
2016-10-19  9:11     ` 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=20161018220408.GA3286@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).