From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: perf mem report segfaulting
Date: Fri, 28 Aug 2015 14:04:14 -0300 [thread overview]
Message-ID: <20150828170414.GG11407@kernel.org> (raw)
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 :-\
- Arnaldo
next reply other threads:[~2015-08-28 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 17:04 Arnaldo Carvalho de Melo [this message]
2015-08-31 8:19 ` perf mem report segfaulting Jiri Olsa
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=20150828170414.GG11407@kernel.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.