From: Johan Tibell <johan.tibell@gmail.com>
To: linux-perf-users@vger.kernel.org
Subject: Re: Symbols not decoded in 0.0.2.PERF
Date: Wed, 20 Apr 2011 10:55:10 +0200 [thread overview]
Message-ID: <BANLkTin0pLU3aGzj8m+4xUeBy5jCNFCLcQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimUitmGOJKMk+YOgXOFNHiLCJCSGQ@mail.gmail.com>
On Tue, Apr 19, 2011 at 5:58 PM, Johan Tibell <johan.tibell@gmail.com> wrote:
> On Tue, Apr 19, 2011 at 1:22 PM, Johan Tibell <johan.tibell@gmail.com> wrote:
>> * 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.
>
> I spent the day making sure this is not the case. All the Haskell
> functions now have the correct (fingers crossed) .type and .size ELF
> directives:
Problem solved. There were indeed some functions that didn't have any
.size directives, making perf (or is that objdump?) fail to recognize
the symbols.
Sorry for the noise.
Johan
prev parent reply other threads:[~2011-04-20 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 11:22 Symbols not decoded in 0.0.2.PERF Johan Tibell
2011-04-19 15:58 ` Johan Tibell
2011-04-20 8:55 ` Johan Tibell [this message]
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=BANLkTin0pLU3aGzj8m+4xUeBy5jCNFCLcQ@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).