From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Brian Marete <marete@toshnix.com>
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: Thu, 1 Dec 2011 12:11:30 -0200 [thread overview]
Message-ID: <20111201141130.GA2323@infradead.org> (raw)
In-Reply-To: <CAHVUoiQC5RjuHUsfPVTQ_C+W0Khp=hQC+_csP0+fJgUnoaALAA@mail.gmail.com>
Em Thu, Dec 01, 2011 at 04:17:49PM +0300, Brian Marete escreveu:
> On Wed, Nov 30, 2011 at 9:10 PM, Arnaldo Carvalho de Melo
> <acme@infradead.org> wrote:
> > https://github.com/acmel/linux/tree/perf/core
> > It just fell thru the cracks, sorry, I should have tried to reproduce
> > and fix this on the tree you reported.
> > But if you can try with the above tree...
> > Persistence is key, thanks for using it :)
> Hello Arnaldo, Thanks for your reply. The perf/core branch of the tree
> you suggest above gives me the same crash (with what looks to me as
> the same b/trace). Would you like the details of the b/trace? The
> master branch of the said tree appears too old to me (so of course it
> does not suffer the crash). Which other branch of the tree should I
> try?
Its just this one, can you try doing something like:
perf top -vvv > /tmp/debug.top 2>&1
bzip2 /tmp/debug.top
That will print lots of information about symbols being loaded,
overlapping maps, etc that can help me understand why that symbol name
looks garbage.
And send me in pvt the result together with a fresh backtrace with those
symbols printed? Also which distro are you using?
- Arnaldo
next prev parent reply other threads:[~2011-12-01 14:11 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
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 [this message]
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=20111201141130.GA2323@infradead.org \
--to=acme@infradead.org \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marete@toshnix.com \
--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).