From: David Hinkle <david.hinkle@securly.com>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: Hadrien Grasland <grasland@lal.in2p3.fr>,
linux-perf-users@vger.kernel.org
Subject: Re: Trying to understand some strange samples in a perf profile
Date: Thu, 28 Dec 2017 15:31:41 -0800 [thread overview]
Message-ID: <CAOrDofTn68XiBjEvF=boM94LwfXUt_W-AhCoOsK7aijiOknyfQ@mail.gmail.com> (raw)
In-Reply-To: <2337765.oK3dqqyzHo@milian-kdab2>
> - build a minimal "unwinder" application for libunwind e.g.
> - notify libunwind about all mmap events
> - install the register and stack state from the per.data file
> - try to unwind, see what happens
I'm having some problems with perf dwarf stack unwindings that stop at
the kernel/userspace boundary and some userspace stacks that aren't
unwinding at all on 4.9.70 I'd really love to shed some light on.
Similar situation, in my case the stacks are in libc-2.17.so, which I
think is symbolized properly (Other traces are unwinding through this
library fine). I'm also using libdw for unwinding and not libunwind.
I'd love to be able to do the above 4 things in an app and see if I
can figure out why it's not unwinding properly. Do you have some
example code that can do that? If you do now or you write it please
share.
next prev parent reply other threads:[~2017-12-28 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 9:39 Trying to understand some strange samples in a perf profile Hadrien Grasland
2017-12-21 9:54 ` Milian Wolff
2017-12-21 10:46 ` Hadrien Grasland
2017-12-21 12:47 ` Milian Wolff
2017-12-21 16:02 ` Hadrien Grasland
2017-12-27 22:21 ` Milian Wolff
2017-12-28 23:31 ` David Hinkle [this message]
2018-01-04 22:08 ` Milian Wolff
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='CAOrDofTn68XiBjEvF=boM94LwfXUt_W-AhCoOsK7aijiOknyfQ@mail.gmail.com' \
--to=david.hinkle@securly.com \
--cc=grasland@lal.in2p3.fr \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.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).