From: Milian Wolff <milian.wolff@kdab.com>
To: David Ahern <dsahern@gmail.com>
Cc: Mark Davis <markdavisinboston@gmail.com>,
linux-perf-users@vger.kernel.org
Subject: Re: Missing stack symbols with perf_event's perf report, despite -fno-omit-frame-pointer compilation
Date: Mon, 25 Apr 2016 11:01:54 +0200 [thread overview]
Message-ID: <1704384.MQzPvE4Oa5@milian-kdab2> (raw)
In-Reply-To: <57157965.4020506@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On Monday, April 18, 2016 6:18:45 PM CEST David Ahern wrote:
> On 4/18/16 6:07 PM, Mark Davis wrote:
> > Auto-detecting system features:
> > ... backtrace: [ on ]
> > ... dwarf: [ OFF ]
> > ... fortify-source: [ on ]
> > ... glibc: [ on ]
> > ... gtk2: [ on ]
> > ... gtk2-infobar: [ on ]
> > ... libaudit: [ OFF ]
> > ... libbfd: [ OFF ]
> > ... libelf: [ OFF ]
>
> Install those 2 development packages.
And if that is still not helping, you may run into the case where the samples
are recorded in a library (like libstdc++, libc,...) which was provided by
your distribution without frame pointers. In such a case, the backtrace will
still be broken.
If you want to use frame pointers, and operate on user space code, my advise
is to recompile all dependencies with frame pointers. On Yocto/Gentoo that is
easily doable, elsewhere you'll have a hard time and waste a ton of time.
I suggest you simply use Dwarf unwinding.
Bye
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next prev parent reply other threads:[~2016-04-25 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 0:07 Missing stack symbols with perf_event's perf report, despite -fno-omit-frame-pointer compilation Mark Davis
2016-04-19 0:18 ` David Ahern
2016-04-25 9:01 ` Milian Wolff [this message]
2016-04-26 1:03 ` Arnaldo Carvalho de Melo
2016-04-19 2:26 ` Taeung Song
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=1704384.MQzPvE4Oa5@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=dsahern@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=markdavisinboston@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).