linux-kernel - Re: [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2)

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: <20120622161449.GL17747@infradead.org>
Date:	Fri, 22 Jun 2012 13:14:49 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	David Ahern <dsahern@...il.com>
Cc:	Namhyung Kim <namhyung@...il.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Jiri Olsa <jolsa@...hat.com>
Subject: Re: [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf
 dependency (v2)

Em Fri, Jun 22, 2012 at 09:35:37AM -0600, David Ahern escreveu:
> On 6/22/12 9:30 AM, Namhyung Kim wrote:
> >>And build-id's are not required for report (-B option for record).

> >>Also, the intent is for a small footprint binary for embedded systems.
> >>On such a system I would expect binaries and libraries to be stripped,
> >>so no point in running perf-archive.

> >But is there a chance that binaries on host still contains symbol (and
> >debug) information even for those cases?
> 
> AFAIK embedded systems do not have the luxury of symbols; the goal
> is as small as possible. All debugging information is left on the
> build servers for off line analysis. That's certainly true for the
> product I work on.

I think at least the .dymsym symbol table is present in DSOs, aka
libraries, otherwise how will they dynamicly link?

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