linux-kernel - Re: [PATCH] perf: Fallback to JIT support for mmap'd non-ELF binaries.

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]

Date:	Thu, 19 Nov 2015 20:31:01 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Brian Robbins <brianrob@...rosoft.com>
Cc:	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	linux-kernel@...r.kernel.org, Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH] perf: Fallback to JIT support for mmap'd non-ELF
 binaries.

On Thu, Nov 19, 2015 at 11:09:07AM -0800, Brian Robbins wrote:
> Programs can execute code contained in files that don't conform
> to the ELF standard.  This is common for cross-platform runtimes
> that support ahead-of-time compilation.  In this case, perf is
> unable to resolve addresses to symbolic names, as the format of
> the mmap'd file is unknown to perf.

I'm assuming you're using PECOFF? Why not teach perf to read those?

Surely there's a library that can parse that stuff, it seems to me Wine
for one needs fairly decent support for this, also GDB (and other
toolchain bits) on Windows targets.

Its just that I was hoping we could move towards getting rid of those
/tmp files now that we have much better JIT support.
--
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/