* Perf on Embedded Systemsp
@ 2015-05-15 13:59 John O'Sullivan
0 siblings, 0 replies; only message in thread
From: John O'Sullivan @ 2015-05-15 13:59 UTC (permalink / raw)
To: linux-perf-users
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-05-15 13:59 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-15 13:59 Perf on Embedded Systemsp John O'Sullivan
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).