linux-kernel - Re: [PATCH V6 0/8] perf tools: kcore improvements

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: <874n8qyt3z.fsf@tassilo.jf.intel.com>
Date:	Wed, 09 Oct 2013 15:30:56 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Adrian Hunter <adrian.hunter@...el.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-kernel@...r.kernel.org, David Ahern <dsahern@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Jiri Olsa <jolsa@...hat.com>, Mike Galbraith <efault@....de>,
	Namhyung Kim <namhyung@...il.com>,
	Paul Mackerras <paulus@...ba.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH V6 0/8] perf tools: kcore improvements

Peter Zijlstra <peterz@...radead.org> writes:

> On Wed, Oct 09, 2013 at 03:01:10PM +0300, Adrian Hunter wrote:
>> 	- workaround objdump difficulties with kcore
>
> I've no idea, but given that've 'inlined' addr2line, should we also
> consider polling in objdump -- or at least that subset of functionality
> that we actually use?

FWIW addr2line is just a straight forward BFD call.

objdump is significantly more complex, a lot of it is outside BFD
(including the full disassembler and all the logic for syncing
the source files)

Another problem is that you would need to sync regularly to keep
up with new instructions.

-Andi


-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/