[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131008140236.GD1348@krava.redhat.com>
Date: Tue, 8 Oct 2013 16:02:36 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org, David Ahern <dsahern@...il.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Mike Galbraith <efault@....de>,
Namhyung Kim <namhyung@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH V5 3/9] perf tools: workaround objdump difficulties with
kcore
On Tue, Oct 08, 2013 at 11:45:50AM +0300, Adrian Hunter wrote:
> objdump fails to annotate module symbols when looking
> at kcore. Workaround this by extracting object code
> from kcore and putting it in a temporary file for
> objdump to use instead. The temporary file is created
> to look like kcore but contains only the function
> being disassembled.
Excited to ses this one, but looks like I'm hitting some
issue. All annotation starts for me like this:
▒
│ Disassembly of section load0: ▒
│ ▒
│ ffffffff815eee80 <load0>: ◆
9.33 │ffffffff815eee80: data32 data32 data32 xchg %ax,%ax
which does not seem right
thanks,
jirka
--
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