Searched refs:unwind (Results 1 – 7 of 7) sorted by relevance
55 std::string unwind; in ErrorMsg() local58 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()
103 std::string unwind; in ErrorMsg() local105 unwind += unwinder->FormatFrame(i) + '\n'; in ErrorMsg()111 function_names.front() + "\n" + "Unwind data:\n" + unwind; in ErrorMsg()
42 // Only need this for arm since libc++ uses its own unwind code that43 // doesn't mix with the other default unwind code.
284 name: "unwind",288 "tools/unwind.cpp",
119 // This forces the creation of eh_frame with unwind information
78 `simpleperf` to unwind the stack via the kernel and frame pointers. Try to
483 The debug-unwind command: debug/test dwarf based offline unwinding, used for debugging simpleperf.1256 3. Can only unwind 64K stack for each sample. So usually can't show complete flame-graph. But1264 stack frame registers. So the kernel can't unwind user stack containing both ARM/THUMB code.