From: Andi Kleen <andi@firstfloor.org>
To: Mauro Andreolini <mauro.andreolini@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-perf-users@vger.kernel.org
Subject: Re: Two questions on perf dwarf callchains
Date: Wed, 22 Jan 2014 18:55:29 +0100 [thread overview]
Message-ID: <20140122175529.GX20765@two.firstfloor.org> (raw)
In-Reply-To: <1390401626.22168.4.camel@nb-andreolini.mat.unimo.it>
On Wed, Jan 22, 2014 at 03:40:26PM +0100, Mauro Andreolini wrote:
> Il giorno sab, 18/01/2014 alle 05.42 +0100, Andi Kleen ha scritto:
> > The dwarf information should be present unless explicitely disabled.
> > It's either a libunwind or compiler problem. You could file a gcc bug
> > I suppose. Also check if gdb can backtrace through it. If that works
> > it's likely unwind.
> gdb can backtrace perfectly through ls -lR /. Also, recompiling the
You tested it on the same IP as perf failed on, correct?
It will depend on the exact location.
> whole system with -fno-omit-frame-pointer makes perf record & report
> work like a charm. So I guess it must be the unwinder.
Please report it to the libunwind developers.
-Andi
next prev parent reply other threads:[~2014-01-22 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 10:21 Two questions on perf dwarf callchains Mauro Andreolini
2014-01-17 20:11 ` Andi Kleen
2014-01-17 23:37 ` Mauro Andreolini
2014-01-18 4:42 ` Andi Kleen
2014-01-22 14:40 ` Mauro Andreolini
2014-01-22 17:55 ` Andi Kleen [this message]
2014-01-22 18:02 ` Mauro Andreolini
2014-01-29 11:18 ` Jiri Olsa
2014-01-29 15:09 ` Mauro Andreolini
2014-01-30 11:47 ` Jiri Olsa
2014-01-30 14:43 ` Mauro Andreolini
2014-01-30 15:40 ` Jiri Olsa
2014-02-03 14:30 ` Mauro Andreolini
2014-02-04 15:28 ` Mauro Andreolini
2014-02-04 15:35 ` Jiri Olsa
2014-02-04 16:01 ` Mauro Andreolini
2014-01-29 13:02 ` Mauro Andreolini
-- strict thread matches above, loose matches on Subject: below --
2014-01-17 23:42 Mauro Andreolini
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=20140122175529.GX20765@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mauro.andreolini@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.