From: Johan Tibell <johan.tibell@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Symbols not decoded in 0.0.2.PERF
Date: Tue, 19 Apr 2011 13:22:02 +0200 [thread overview]
Message-ID: <BANLkTike-f9qjdtjce+uiAPrjXgucn=5xQ@mail.gmail.com> (raw)
Hi,
I'm trying to use perf record/report on a non-stripped, Haskell binary
(i.e. compiled using GHC). Unfortunately, not all symbols are
decoded*:
75.28% bench ./bench [.] 0x000000002b612b
7.11% bench /lib/libc-2.11.1.so [.] memcpy
5.47% bench ./bench [.] 0x0000000000438f
3.47% bench ./bench [.] allocate
1.86% bench ./bench [.] s1Ol_info
1.65% bench ./bench [.] s1Ok_info
0.62% bench ./bench [.] memcpy@plt
0.48% bench ./bench [.] clearNurseries
0.33% bench ./bench [.] evacuate1
0.24% bench ./bench [.] GarbageCollect
How can I figure out what 0x000000002b612b corresponds to?
perf version: 0.0.2.PERF (installed from Ubuntu package)
Kernel version: 2.6.32
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 44
model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
* It could be the case that GHC is generating symbols that perf cannot
interpret somehow. If we can confirm this is the case we can try to
fix that.
-- Johan
next reply other threads:[~2011-04-19 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 11:22 Johan Tibell [this message]
2011-04-19 15:58 ` Symbols not decoded in 0.0.2.PERF Johan Tibell
2011-04-20 8:55 ` Johan Tibell
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='BANLkTike-f9qjdtjce+uiAPrjXgucn=5xQ@mail.gmail.com' \
--to=johan.tibell@gmail.com \
--cc=linux-perf-users@vger.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;
as well as URLs for NNTP newsgroup(s).