From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752793AbbHaIUF (ORCPT <rfc822;w@1wt.eu>);
	Mon, 31 Aug 2015 04:20:05 -0400
Received: from mx1.redhat.com ([209.132.183.28]:57035 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752606AbbHaIUA (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 31 Aug 2015 04:20:00 -0400
Date: Mon, 31 Aug 2015 10:19:57 +0200
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Stephane Eranian <eranian@google.com>, Namhyung Kim <namhyung@kernel.org>,
        Jiri Olsa <jolsa@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: perf mem report segfaulting
Message-ID: <20150831081957.GC22039@krava.brq.redhat.com>
References: <20150828170414.GG11407@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150828170414.GG11407@kernel.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Aug 28, 2015 at 02:04:14PM -0300, Arnaldo Carvalho de Melo wrote:
> 
> Hi,
> 
> 	While trying to test my tmp.perf/ui_browser.horiz_scroll branch
> with 'perf mem report' to allow that kind of browsing on the TUI, as of
> now it works only on --stdio mode, using the right/left arrow keys, I
> noticed this in acme/perf/core (but I saw it too in many previous
> revisions, trying to bisect it):
> 
> [root@zoo ~]# perf mem record -a
> ^C[ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 3.072 MB perf.data (647 samples) ]
> 
> [root@zoo ~]# perf mem report
> perf: Segmentation fault
> -------- backtrace --------
> perf[0x52a08b]
> /lib64/libc.so.6(+0x34960)[0x7f8726860960]
> perf(addr_map_symbol__inc_samples+0xbb)[0x47abfb]
> perf[0x42e93f]
> perf(hist_entry_iter__add+0x102)[0x4d9632]
> perf[0x42e7ba]
> perf[0x4bc4c3]
> perf[0x4bc9c1]
> perf[0x4bf6b9]
> perf(perf_session__process_events+0x390)[0x4be1b0]
> perf(cmd_report+0x1038)[0x42faf8]
> perf(cmd_mem+0x3ec)[0x44c69c]
> perf[0x479113]
> perf(main+0x60a)[0x420a5a]
> /lib64/libc.so.6(__libc_start_main+0xf0)[0x7f872684bfe0]
> perf[0x420b79]
> [0x0]
> [root@zoo ~]# perf evlist
> cpu/mem-loads/pp
> cpu/mem-stores/pp
> [root@zoo ~]#
> 
> Have you noticed this? No time to look at this now :-\

cannot reproduce it on your perf/core.. did you navigate
to anything specific to trigger it?

jirka