Lines Matching refs:dwarf

25 …ays get complete DWARF-based call graphs](#why-we-cant-always-get-complete-dwarf-based-call-graphs)
44    a. When recording dwarf based call graph, simpleperf unwinds the stack before writing a sample
124 which may not support profiling features like recording dwarf based call graphs.
131 Below is our experiences of dwarf based call graphs and stack frame based call graphs.
133 dwarf based call graphs:
149 5. Take less CPU time than dwarf based call graphs. So the sample frequency can be 4000 Hz or
152 So if you need to profile code on ARM or profile fully compiled Java code, dwarf based call graphs
154 better. After all, you can always try dwarf based call graph first, because it always produces
158 Simpleperf may need unstripped native binaries on the device to generate good dwarf based call
166 64KB stack data is dumped by the kernel. By unwinding the stack based on dwarf information, we get
200 When using dwarf based call graphs, simpleperf generates callchains during recording to save space.