From: Namhyung Kim <namhyung@gmail.com>
To: Milian Wolff <mail@milianw.de>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kenel.org>
Subject: Re: missing mmap events in perf profiles without dwarf callgraph
Date: Tue, 19 Jan 2021 18:36:11 +0900 [thread overview]
Message-ID: <CAM9d7cihUNLX9wAWkNi5-J1HC4NPhD_mFW9EFc77t=SAFF10-A@mail.gmail.com> (raw)
In-Reply-To: <7161646.QLfhZlOSzD@milian-workstation>
Hi Milian,
On Tue, Jan 19, 2021 at 5:11 PM Milian Wolff <mail@milianw.de> wrote:
>
> On Donnerstag, 14. Januar 2021 09:56:36 CET Namhyung Kim wrote:
> > What I noticed is ss->adjust_symbols which is set for user DSOs. It does
> >
> > sym.st_value -= shdr.sh_addr - shdr.sh_offset
> >
> > Maybe your program's section header has different values?
>
> Hey Namhyung,
>
> how would I figure that one out? Isn't that data shown in the readelf output
> above? Put differently: Could someone else maybe show his readelf output so we
> can compare?
I mean the below. In my case, address and offset of the .text section are
same as 0x1080.
Thanks,
Namhyung
$ readelf -S a.out
There are 37 section headers, starting at offset 0x1df20:
Section Headers:
[Nr] Name Type Address Offset
Size EntSize Flags Link Info Align
[ 0] NULL 0000000000000000 00000000
0000000000000000 0000000000000000 0 0 0
[ 1] .interp PROGBITS 00000000000002a8 000002a8
000000000000001c 0000000000000000 A 0 0 1
[ 2] .note.gnu.bu[...] NOTE 00000000000002c4 000002c4
0000000000000024 0000000000000000 A 0 0 4
[ 3] .note.ABI-tag NOTE 00000000000002e8 000002e8
0000000000000020 0000000000000000 A 0 0 4
[ 4] .gnu.hash GNU_HASH 0000000000000308 00000308
0000000000000028 0000000000000000 A 5 0 8
[ 5] .dynsym DYNSYM 0000000000000330 00000330
0000000000000138 0000000000000018 A 6 1 8
[ 6] .dynstr STRTAB 0000000000000468 00000468
00000000000000fb 0000000000000000 A 0 0 1
[ 7] .gnu.version VERSYM 0000000000000564 00000564
000000000000001a 0000000000000002 A 5 0 2
[ 8] .gnu.version_r VERNEED 0000000000000580 00000580
0000000000000040 0000000000000000 A 6 2 8
[ 9] .rela.dyn RELA 00000000000005c0 000005c0
0000000000000108 0000000000000018 A 5 0 8
[10] .rela.plt RELA 00000000000006c8 000006c8
0000000000000060 0000000000000018 AI 5 23 8
[11] .init PROGBITS 0000000000001000 00001000
0000000000000017 0000000000000000 AX 0 0 4
[12] .plt PROGBITS 0000000000001020 00001020
0000000000000050 0000000000000010 AX 0 0 16
[13] .plt.got PROGBITS 0000000000001070 00001070
0000000000000008 0000000000000008 AX 0 0 8
[14] .text PROGBITS 0000000000001080 00001080
000000000000201e 0000000000000000 AX 0 0 16
...
next prev parent reply other threads:[~2021-01-19 18:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 16:56 missing mmap events in perf profiles without dwarf callgraph Milian Wolff
2021-01-13 10:30 ` Jiri Olsa
2021-01-13 17:47 ` Milian Wolff
2021-01-13 18:45 ` Jiri Olsa
2021-01-13 19:18 ` Milian Wolff
2021-01-14 8:56 ` Namhyung Kim
2021-01-19 8:09 ` Milian Wolff
2021-01-19 9:36 ` Namhyung Kim [this message]
2021-01-19 11:33 ` 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='CAM9d7cihUNLX9wAWkNi5-J1HC4NPhD_mFW9EFc77t=SAFF10-A@mail.gmail.com' \
--to=namhyung@gmail.com \
--cc=acme@kenel.org \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mail@milianw.de \
/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).