linux-kernel - Re: [RFC] The -Og debugging experience

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 7 Dec 2015 14:45:42 +0100
From:	Jiri Olsa <jolsa@...hat.com>
To:	Martin Liška <mliska@...e.cz>
Cc:	Jiri Olsa <jolsa@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	David Ahern <dsahern@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [RFC] The -Og debugging experience

On Mon, Dec 07, 2015 at 11:48:07AM +0100, Martin Liška wrote:
> On 12/02/2015 05:48 PM, Jiri Olsa wrote:
> > heya,
> > using the -Og for DEBUG=1 builds gives me many 'optimized out' stuff
> > 
> > It was introduced in here:
> >   e8b7ea4356fd perf tools: Improve setting of gcc debug option
> > 
> > - here's backtrace from segfault I was looking at, current code:
> 
> Hi.
> 
> Can you please provide a test-case which I can use for testing of the issue?

just run perf report in gdb and kill it with sigsegv from other terminal
this gives me several instances of <optimized out> right in the backtrace

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