Linux Perf Users
 help / color / mirror / Atom feed
* Records call-graphs on ARM, reporting on x86_64
@ 2018-02-08 16:13 Vuille, Martin (Martin)
  2018-02-08 16:30 ` Milian Wolff
  0 siblings, 1 reply; 8+ messages in thread
From: Vuille, Martin (Martin) @ 2018-02-08 16:13 UTC (permalink / raw)
  To: linux-perf-users@vger.kernel.org

I would like to collect call-graphs on my ARM target and examine them on my x86_64 host.
I have no debug info on the ARM target; it is available on the x86_64 host.

On the ARM, I am passing the '--call-graph dwarf' option to 'perf record'.
As I understand it, this collects user stacks for each event and the unwinding is done by
'perf report' using DWARF debug info.

When I look at the data with 'perf report', most of the call stacks contain "bogus" addresses
that are in data (e.g., stack) or unmapped areas of the process address space. (This is pure
C/C++ code, there's no JITing that I know of.)

What I am unclear about is whether DWARF is DWARF or whether there are "ARM DWARF"
and "x86_64 DWARF". And if the latter is true, what do I need to do to interpret "ARM DWARF"
on my x86_64 host?

MV

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2018-02-12 16:37 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-08 16:13 Records call-graphs on ARM, reporting on x86_64 Vuille, Martin (Martin)
2018-02-08 16:30 ` Milian Wolff
2018-02-08 17:09   ` Vuille, Martin (Martin)
2018-02-09 18:06     ` Vuille, Martin (Martin)
2018-02-09 20:56       ` Kim Phillips
2018-02-09 23:26         ` Vuille, Martin (Martin)
2018-02-12  8:28           ` Jiri Olsa
2018-02-12 16:37             ` Vuille, Martin (Martin)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox