[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHVUoiR=gMcdLZcR+TmB6CiRhEP+x8aXjR5r5Wc4k6gZwzLAjg@mail.gmail.com>
Date: Tue, 6 Dec 2011 10:22:57 +0300
From: Brian Gitonga Marete <marete@...hnix.com>
To: Arnaldo Carvalho de Melo <acme@...radead.org>
Cc: David Ahern <dsahern@...il.com>, linux-kernel@...r.kernel.org,
mingo@...e.hu, peterz@...radead.org, fweisbec@...il.com
Subject: Re: [PATCH] perf top: fix crash on annotate request
On Thu, Dec 1, 2011 at 5:11 PM, Arnaldo Carvalho de Melo
<acme@...radead.org> wrote:
>
> 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?
>
Hello Arnaldo. Curiously, I am unable to reproduce the crash when
stdout is redirected to a file. I am able to capture lots of output if
I redirect stdout to a file in verbose mode, but it won't crash when I
do that. Just the same, I am still able to always reproduce (within a
few seconds) with your perf/core branch on the tree you pointed me to.
This time, I did a `thread apply all bt' in gdb to show the trace for
the UI thread since it now seems to me to probably have something with
the UI output (because I cannot reproduce if o/put is to a file). The
trace is attached in the file gdb.txt.
Is the `perf top -vvv > /tmp/debug.top 2>&1' output useful even if it
is captured in a session that does not crash? If so will send the
output privately to you.
I am using Ubuntu 10.10
Thanks!
--
Brian Gitonga Marete
Toshnix Systems
Tel: +254722151590
View attachment "gdb.txt" of type "text/plain" (5355 bytes)
Powered by blists - more mailing lists