From: Brian Marete <marete@toshnix.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: David Ahern <dsahern@gmail.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu,
peterz@infradead.org, fweisbec@gmail.com
Subject: Re: [PATCH] perf top: fix crash on annotate request
Date: Fri, 11 Nov 2011 01:01:47 +0300 [thread overview]
Message-ID: <CAHVUoiSwem2r9J==gmHPfst3_0ZB5bd0ykf9cPUMdhZFaXC9EA@mail.gmail.com> (raw)
In-Reply-To: <20111020130041.GB1772@ghostprotocols.net>
Hello,
On Thu, Oct 20, 2011 at 4:00 PM, Arnaldo Carvalho de Melo
<acme@ghostprotocols.net> wrote:
> I.e. the map_ip for this method is messing up things, what symbol is
> this? I.e. please provide:
>
> p *sym
> p *map
I have am experiencing the same segfault using perf from the latest
linus' tree. The gdb backtrace is below. Which patch fixes it? Or is
it already fixed in some git tree on kernel.org?
Thanks
Program received signal SIGSEGV, Segmentation fault.
0x000000000042e27e in symbol__inc_addr_samples (sym=0x1279e70, map=0x9677a0,
evidx=0, addr=256544) at util/annotate.c:73
73 h->addr[offset]++;
#0 0x000000000042e27e in symbol__inc_addr_samples (sym=0x1279e70, map=
0x9677a0, evidx=0, addr=256544) at util/annotate.c:73
#1 0x00000000004215e4 in record_precise_ip (he=0x1e7b260, counter=0,
ip=256544) at builtin-top.c:223
#2 0x0000000000422ba1 in perf_event__process_sample (event=0x7ffff7ec4c60,
evsel=0x837a10, sample=0x7fffffffe340, session=0x837e80)
at builtin-top.c:801
#3 0x0000000000422c8c in perf_session__mmap_read_idx (self=0x837e80, idx=1)
at builtin-top.c:825
#4 0x0000000000422d43 in perf_session__mmap_read (self=0x837e80)
at builtin-top.c:839
#5 0x0000000000423295 in __cmd_top () at builtin-top.c:1003
#6 0x0000000000423940 in cmd_top (argc=0, argv=0x7fffffffe720, prefix=0x0)
at builtin-top.c:1274
#7 0x000000000040ffdc in run_builtin (p=0x6a4bc8, argc=1, argv=0x7fffffffe720)
at perf.c:286
#8 0x00000000004101af in handle_internal_command (argc=1, argv=0x7fffffffe720)
at perf.c:358
#9 0x00000000004102b5 in run_argv (argcp=0x7fffffffe60c, argv=0x7fffffffe600)
at perf.c:402
#10 0x00000000004104f8 in main (argc=1, argv=0x7fffffffe720) at perf.c:512
# Output of p *sym
$1 = {rb_node = {rb_parent_color = 19423281, rb_right = 0x0, rb_left = 0x0},
start = 1124896, end = 1126163, namelen = 16, binding = 0 '\000',
ignore = false, name = 0x1279e70 "1`(\001"}
# Output of p *map
$2 = {{rb_node = {rb_parent_color = 9861408, rb_right = 0x967860, rb_left =
0x9676e0}, node = {next = 0x967920, prev = 0x967860}}, start = 4142972928,
end = 4144365568, type = 0 '\000', referenced = true, priv = 0, pgoff = 0,
map_ip = 0x44fc69 <map__map_ip>, unmap_ip = 0x44fc92 <map__unmap_ip>, dso =
0x8e5490, groups = 0x964cd8}
--
Brian Gitonga Marete
Toshnix Systems
Tel: +254722151590
next prev parent reply other threads:[~2011-11-10 22:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 18:23 [PATCH] perf top: fix crash on annotate request David Ahern
2011-10-19 18:38 ` Arnaldo Carvalho de Melo
2011-10-19 18:44 ` David Ahern
2011-10-19 19:20 ` Arnaldo Carvalho de Melo
2011-10-19 20:21 ` David Ahern
2011-10-19 21:39 ` David Ahern
2011-10-20 12:51 ` Arnaldo Carvalho de Melo
2011-10-19 22:12 ` David Ahern
2011-10-20 13:00 ` Arnaldo Carvalho de Melo
2011-10-20 14:15 ` David Ahern
2011-11-10 22:01 ` Brian Marete [this message]
2011-11-13 13:43 ` Arnaldo Carvalho de Melo
2011-11-13 21:03 ` Brian Marete
2011-11-13 21:42 ` Brian Marete
2011-11-30 13:23 ` Brian Marete
2011-11-30 18:10 ` Arnaldo Carvalho de Melo
2011-12-01 13:17 ` Brian Marete
2011-12-01 14:11 ` Arnaldo Carvalho de Melo
2011-12-06 7:22 ` Brian Gitonga Marete
2011-12-06 13:44 ` Arnaldo Carvalho de Melo
2011-12-15 21:01 ` Brian Gitonga Marete
2011-12-15 22:04 ` Brian Gitonga Marete
2011-12-16 23:46 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2011-10-20 20:39 David Ahern
2011-10-20 21:30 ` Arnaldo Carvalho de Melo
2011-10-20 23:26 ` 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='CAHVUoiSwem2r9J==gmHPfst3_0ZB5bd0ykf9cPUMdhZFaXC9EA@mail.gmail.com' \
--to=marete@toshnix.com \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).