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: <1301418533.2250.419.camel@laptop>
Date:	Tue, 29 Mar 2011 19:08:53 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] perf report: add sort by file lines

On Tue, 2011-03-29 at 19:06 +0200, Peter Zijlstra wrote:
> On Tue, 2011-03-29 at 19:03 +0200, Peter Zijlstra wrote:
> > > Is it an unwind of the call frame stack to find out what data member was
> > > accessed?
> > 
> > No need to unwind stacks, DWARF should have information on function
> > local stack. It should be able to tell you the type of things like -8(%
> > rbp). 
> 
> That is, we don't even have a life stack to unwind, so we simply cannot
> unwind at all, but the debug information should be able to tell you the
> type of whatever would live at a certain stack position if we were to
> have a stack.

Furthermore, I've now completely exhausted my knowledge of debuginfo and
hope Masami and Arnaldo will help with further details ;-)

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ