From: Jiri Olsa <jolsa@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC] The -Og debugging experience
Date: Mon, 7 Dec 2015 14:45:42 +0100 [thread overview]
Message-ID: <20151207134542.GB26191@krava.brq.redhat.com> (raw)
In-Reply-To: <566563E7.9040706@suse.cz>
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
next prev parent reply other threads:[~2015-12-07 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 16:48 Jiri Olsa
2015-12-03 8:29 ` Ingo Molnar
2015-12-07 10:48 ` Martin Liška
2015-12-07 13:45 ` Jiri Olsa [this message]
2015-12-07 14:04 ` Martin Liška
2015-12-07 14:16 ` Jiri Olsa
2015-12-10 13:07 ` Martin Liška
2015-12-10 13:24 ` Jiri Olsa
2015-12-10 15:13 ` Arnaldo Carvalho de Melo
2015-12-11 9:17 ` Martin Liška
2015-12-14 8:15 ` [tip:perf/core] Revert "perf tools: Improve setting of gcc debug option" tip-bot for Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151207134542.GB26191@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mliska@suse.cz \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®