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
Date: Mon, 31 Aug 2015 10:19:57 +0200 [thread overview]
Message-ID: <20150831081957.GC22039@krava.brq.redhat.com> (raw)
In-Reply-To: <20150828170414.GG11407@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
next prev parent reply other threads:[~2015-08-31 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 17:04 Arnaldo Carvalho de Melo
2015-08-31 8:19 ` Jiri Olsa [this message]
2015-08-31 14:23 ` Arnaldo Carvalho de Melo
2015-08-31 15:32 ` Namhyung Kim
2015-08-31 15:56 ` Arnaldo Carvalho de Melo
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=20150831081957.GC22039@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.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
Powered by JetHome