[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111206134431.GA10709@infradead.org>
Date: Tue, 6 Dec 2011 11:44:31 -0200
From: Arnaldo Carvalho de Melo <acme@...radead.org>
To: Brian Gitonga Marete <marete@...hnix.com>
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
Em Tue, Dec 06, 2011 at 10:22:57AM +0300, Brian Gitonga Marete escreveu:
> 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
That is good input, so can you please try using just:
perf top --stdio
I.e. probably the problem is with the TUI code and running it in --stdio
mode will help us pinpoint that. No need to redirect anything.
> 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.
please.
> I am using Ubuntu 10.10
Ok,
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists