From: Milian Wolff <milian.wolff@kdab.com>
To: linux-perf-users@vger.kernel.org
Cc: namhyung@kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: kallsyms in buildid - broken mapping?
Date: Tue, 27 Jun 2017 16:16:47 +0200 [thread overview]
Message-ID: <6006405.Fli7mH7B85@milian-kdab2> (raw)
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
Hey all,
a colleague of mine just sent me a `perf archive` tarball and the accompanying
perf.data file. The tarball contains a kallsyms entry with build-id for
`[kernel.kallsyms]`. But the file seems to be bogus, it only contains "null"
mappings, i.e.:
$ head kallsyms
0000000000000000 A irq_stack_union
0000000000000000 A __per_cpu_start
0000000000000000 A exception_stacks
0000000000000000 A gdt_page
0000000000000000 A espfix_waddr
0000000000000000 A espfix_stack
0000000000000000 A cpu_info
0000000000000000 A cpu_llc_shared_map
0000000000000000 A cpu_core_map
0000000000000000 A cpu_sibling_map
$ cut -f1 -d' ' < kallsyms | uniq -c
144971 0000000000000000
He now also sent me a copy of `/proc/kallsyms` which actually seems to contain
a useful mapping. Any idea what lead to the broken original mapping?
Thanks
--
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: 3826 bytes --]
next reply other threads:[~2017-06-27 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 14:16 Milian Wolff [this message]
2017-06-27 14:25 ` kallsyms in buildid - broken mapping? Kim Phillips
2017-06-27 22:00 ` 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=6006405.Fli7mH7B85@milian-kdab2 \
--to=milian.wolff@kdab.com \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
/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