From: Mark Wielaard <mark@klomp.org>
To: Milian Wolff <mail@milianw.de>, elfutils-devel@sourceware.org
Cc: Ulf Hermann <ulf.hermann@qt.io>,
Christoph Sterz <christoph.sterz@kdab.com>
Subject: Re: Handling pgoff in perf elf mmap/mmap2 elf info
Date: Mon, 15 Oct 2018 21:05:00 -0000 [thread overview]
Message-ID: <1539637492.4578.20.camel@klomp.org> (raw)
In-Reply-To: <4862287.LsxLGO1v19@agathebauer>
Hi Milian,
On Mon, 2018-10-15 at 22:38 +0200, Milian Wolff wrote:
> here's one example of mmap events recorded by perf:
>
> 0x7fac5ec0b000 to 0x7fac5ed9a000, len = 0x18f000, offset = 0
> r--p /usr/lib/libstdc++.so.6.0.25
> 0x7fac5ec94000 to 0x7fac5ed8a000, len = 0xf6000, offset = 0x89000
> ---p /usr/lib/libstdc++.so.6.0.25
> 0x7fac5ec94000 to 0x7fac5ed4c000, len = 0xb8000, offset = 0x89000
> r-xp /usr/lib/libstdc++.so.6.0.25
> 0x7fac5ed4c000 to 0x7fac5ed89000, len = 0x3d000, offset = 0x141000
> r--p /usr/lib/libstdc++.so.6.0.25
> 0x7fac5ed8a000 to 0x7fac5ed97000, len = 0xd000, offset = 0x17e000
> rw-p /usr/lib/libstdc++.so.6.0.25
Could you also post the matching phdr output for the file?
eu-readelf -l /usr/lib/libstdc++.so.6.0.25 should show it.
That way we can see how the PT_LOAD segments map to the mmap events.
Thanks,
Mark
next prev parent reply other threads:[~2018-10-15 21:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 12:12 Christoph Sterz
2018-09-19 12:24 ` Ulf Hermann
2018-09-21 13:07 ` Mark Wielaard
2018-09-21 13:35 ` Ulf Hermann
2018-09-26 14:38 ` Milian Wolff
2018-10-09 20:33 ` Milian Wolff
2018-10-11 17:02 ` Ulf Hermann
2018-10-11 17:37 ` Mark Wielaard
2018-10-11 18:14 ` Milian Wolff
2018-10-15 20:39 ` Milian Wolff
2018-10-15 21:05 ` Mark Wielaard [this message]
2018-10-15 21:06 ` Milian Wolff
2018-10-17 14:52 ` Milian Wolff
2018-10-17 22:26 ` Mark Wielaard
2018-10-18 7:41 ` Ulf Hermann
2018-10-20 10:49 ` Milian Wolff
2018-10-15 20:48 ` 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=1539637492.4578.20.camel@klomp.org \
--to=mark@klomp.org \
--cc=christoph.sterz@kdab.com \
--cc=elfutils-devel@sourceware.org \
--cc=mail@milianw.de \
--cc=ulf.hermann@qt.io \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).