From: Kim Phillips <kim.phillips@arm.com>
To: "Vuille, Martin (Martin)" <vmartin@avaya.com>
Cc: Milian Wolff <milian.wolff@kdab.com>,
"linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>
Subject: Re: Not finding symbol information
Date: Mon, 5 Feb 2018 17:35:41 -0600 [thread overview]
Message-ID: <20180205173541.ce7e8fdf3d4c9230a2a70c96@arm.com> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE6521910377989260A050@AZ-US1EXMB02.global.avaya.com>
On Sat, 3 Feb 2018 03:30:02 +0000
"Vuille, Martin (Martin)" <vmartin@avaya.com> wrote:
> BTW, I found some odd behaviour around that too. 'perf report --symfs PATH' is
> looking for the buildid cache in 'PATH/$HOME/.debug', not '$HOME/.debug'.
> Not sure whether that's design intent or a bug.
Yeah, that doesn't sound right: the manpage just says "Look for files
with symbols relative to this directory."
> > It might also be worth trying running the report on the target, if possible. I'll
> > try and take a look next week...I need to revive my
> > arm32 boxes...
>
> Unfortunately the stripped binaries just barely fit on the target, so getting the
> debug info on there is out of the question.
OK, in that case can you try cherry-picking commit 9b200653518e "perf
symbols: Take into account symfs setting when reading file build ID"?
It looks highly relevant but I haven't been able to make sure yet.
Thanks,
Kim
next prev parent reply other threads:[~2018-02-05 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 14:06 Not finding symbol information Vuille, Martin (Martin)
2018-02-02 14:31 ` Milian Wolff
2018-02-03 0:38 ` Kim Phillips
2018-02-03 3:30 ` Vuille, Martin (Martin)
2018-02-05 23:35 ` Kim Phillips [this message]
2018-02-06 2:13 ` Vuille, Martin (Martin)
2018-02-06 13:09 ` Vuille, Martin (Martin)
2018-02-06 13:20 ` Vuille, Martin (Martin)
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=20180205173541.ce7e8fdf3d4c9230a2a70c96@arm.com \
--to=kim.phillips@arm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=vmartin@avaya.com \
/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).