All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John O'Sullivan" <john.osullivan@cloudiumsystems.com>
To: linux-perf-users@vger.kernel.org
Subject: Perf on Embedded Systemsp
Date: Fri, 15 May 2015 14:59:36 +0100	[thread overview]
Message-ID: <5555FBC8.2090404@cloudiumsystems.com> (raw)

Hi,
I have been trying without success to get perf running on an arm board. 
I have written a sample application (called sample_static_application) 
and it links to a static library.
In linking the file I use the linker directive (as advised in 
https://perf.wiki.kernel.org/index.php/Tutorial)

After I generate my binary I do the following:
arm-xilinx-linux-gnueabi-objcopy --only-keep-debug 
./sample_static_application sample_static_application.debug

as suggested in 
(http://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html)
I copy both of these files to
/usr/bin
so that I have
/usr/bin/sample_static_application
and
/usr/bin/sample_static_application.debug
When I run perf I get:
Failed to open /usr/bin/sample_static_application, continuing without 
symbols

If I run perf buildid-cache and then run perf buildid-list I just get
5b52.....................................255a [kernel-kallsyms]

What do I need to do to be able to see the symbols for my 
sample_static_application? I have searched the web for days without any 
luck.
Is there some way to register the .debug files or should perf just find 
them, where does it look for them.

I know there is a command

perf-buildid-cache --add , but what format is this looking for and how would I add my application symbols using this command.


Just for the record I also copied sample_static_application.debug to /usr/bin/debug and /usr/bin/.debug but still I get the same message:
Failed to open /usr/bin/sample_static_application, continuing without symbols

Any suggestions?

regards
John

                 reply	other threads:[~2015-05-15 13:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5555FBC8.2090404@cloudiumsystems.com \
    --to=john.osullivan@cloudiumsystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.