linux-kernel - Re: [PATCH V5 3/9] perf tools: workaround objdump difficulties with kcore

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <525506C5.3020101@intel.com>
Date:	Wed, 09 Oct 2013 10:33:25 +0300
From:	Adrian Hunter <adrian.hunter@...el.com>
To:	Jiri Olsa <jolsa@...hat.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 08/10/13 17:02, Jiri Olsa wrote:
> 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

Can you tell me the commits of the kernel and perf tools you
were using, plus the commands and what symbol it was?

--
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/