From: Arun Sharma <asharma@fb.com>
To: linux-perf-users@vger.kernel.org
Cc: Sam Liao <phyomh@gmail.com>
Subject: [BUG] perf report core dump
Date: Fri, 10 Jun 2011 16:15:54 -0700 [thread overview]
Message-ID: <4DF2A5AA.90409@fb.com> (raw)
This happens only with --tui. --stdio is ok for some strange reason.
Core was generated by `perf report -g fractal 0.5 caller --sort pid'.
Program terminated with signal 11, Segmentation fault.
#0 symbol__inc_addr_samples (sym=0xacf360, map=<value optimized out>,
evidx=0, addr=179753205) at util/annotate.c:71
71 util/annotate.c: No such file or directory.
in util/annotate.c
(gdb) bt
#0 symbol__inc_addr_samples (sym=0xacf360, map=<value optimized out>,
evidx=0, addr=179753205) at util/annotate.c:71
#1 0x000000000040ec7a in process_sample_event (event=<value optimized
out>, sample=0x7fff5a631400, evsel=0x7cbed0, session=0x7ca2c0)
at builtin-report.c:92
#2 0x000000000043e8a4 in __perf_session__process_events
(session=0x7ca2c0, data_offset=<value optimized out>, data_size=<value
optimized out>,
file_size=7730296, ops=0x689340) at util/session.c:511
#3 0x000000000043ee0a in perf_session__process_events (self=0x7ca2c0,
ops=0x689340) at util/session.c:1117
#4 0x000000000040ef40 in cmd_report (argc=0, argv=<value optimized
out>, prefix=<value optimized out>) at builtin-report.c:272
#5 0x000000000040565b in handle_internal_command (argc=5,
argv=0x7fff5a632830) at perf.c:286
(gdb) x /i $rip
0x41e3cd <symbol__inc_addr_samples+173>: mov 0x8(%rdx,%rcx,8),%rax
(gdb) p /x addr - sym->start
$9 = 0xffffffffdc290285
util/annotate.c
68 offset = addr - sym->start;
69 h = annotation__histogram(notes, evidx);
70 h->sum++;
71 h->addr[offset]++;
Not sure why offset is negative here. We might need some extra checks.
-Arun
next reply other threads:[~2011-06-10 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 23:15 Arun Sharma [this message]
2011-06-11 16:24 ` [BUG] perf report core dump Sam Liao
2011-06-13 20:16 ` Arun Sharma
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=4DF2A5AA.90409@fb.com \
--to=asharma@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=phyomh@gmail.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 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.