Home
last modified time | relevance | path

Searched refs:unwind (Results 1 – 9 of 9) sorted by relevance

/system/core/libunwindstack/tests/
DLocalUnwinderTest.cpp55 std::string unwind; in ErrorMsg() local
58 unwind += android::base::StringPrintf("#%02zu pc 0x%" PRIx64 " rel_pc 0x%" PRIx64, i++, in ErrorMsg()
62 unwind += " " + frame.map_info->name; in ErrorMsg()
64 unwind += android::base::StringPrintf(" 0x%" PRIx64 "-0x%" PRIx64, frame.map_info->start, in ErrorMsg()
68 unwind += android::base::StringPrintf(" offset 0x%" PRIx64, frame.map_info->offset); in ErrorMsg()
72 unwind += " " + frame.function_name; in ErrorMsg()
74 unwind += android::base::StringPrintf("+%" PRId64, frame.function_offset); in ErrorMsg()
77 unwind += '\n'; in ErrorMsg()
83 function_names.front() + "\n" + "Unwind data:\n" + unwind; in ErrorMsg()
DVerifyBionicTerminationTest.cpp41 std::string unwind; in DumpFrames() local
43 unwind += unwinder.FormatFrame(i) + '\n'; in DumpFrames()
45 return unwind; in DumpFrames()
DUnwindTest.cpp103 std::string unwind; in ErrorMsg() local
105 unwind += unwinder->FormatFrame(i) + '\n'; in ErrorMsg()
111 function_names.front() + "\n" + "Unwind data:\n" + unwind; in ErrorMsg()
/system/core/libunwindstack/
DAndroidVersions.md6 on different versions. It also describes the different way an unwind
24 versions of Android will not unwind properly in this case. For apps that
51 other way this has been observed is when running simpleperf to unwind since
55 be correct since the eh\_frame information was enough to do the unwind
59 to do an unwind.
61 to unreadable memory. As long as the code can find the unwind tables,
84 continuing to unwind even when encountering Dwarf 5 elf files.
87 unwind was correct, only the frame in the signal handler was incorrect
112 * Fix bug in load bias handling. If the unwind information in the eh\_frame
114 and uses pc relative FDEs, the unwind will be incorrect. This tends
[all …]
DAndroid.bp398 name: "unwind",
402 "tools/unwind.cpp",
/system/core/libbacktrace/
DAndroid.bp166 // This forces the creation of eh_frame with unwind information
/system/extras/simpleperf/doc/
DREADME.md135 3. Can only unwind 64K stack for each sample. So usually can't show complete flamegraph. But
143 stack frame registers. So the kernel can't unwind user stack containing both ARM/THUMB code.
188 The debug information needed to unwind C functions is in .debug_frame section, which is usually
Dinferno.md78 `simpleperf` to unwind the stack via the kernel and frame pointers. Try to
Dexecutable_commands_reference.md68 The debug-unwind command: debug/test dwarf based offline unwinding, used for debugging simpleperf.