| /aosp12/system/unwinding/libunwindstack/tests/ |
| H A D | LocalUnwinderTest.cpp | 55 std::string unwind; in ErrorMsg() local
58 unwind += android::base::StringPrintf("#%02zu pc 0x%" PRIx64 " rel_pc 0x%" PRIx64, i++, in ErrorMsg()
62 unwind += " "; in ErrorMsg()
63 unwind += frame.map_info->name(); in ErrorMsg()
65 unwind += android::base::StringPrintf(" 0x%" PRIx64 "-0x%" PRIx64, frame.map_info->start(), in ErrorMsg()
69 unwind += android::base::StringPrintf(" offset 0x%" PRIx64, frame.map_info->offset()); in ErrorMsg()
73 unwind += " " + frame.function_name; in ErrorMsg()
75 unwind += android::base::StringPrintf("+%" PRId64, frame.function_offset); in ErrorMsg()
78 unwind += '\n'; in ErrorMsg()
84 function_names.front() + "\n" + "Unwind data:\n" + unwind; in ErrorMsg()
|
| H A D | VerifyBionicTerminationTest.cpp | 41 std::string unwind; in DumpFrames() local
43 unwind += unwinder.FormatFrame(i) + '\n'; in DumpFrames()
45 return unwind; in DumpFrames()
|
| H A D | UnwindTest.cpp | 105 std::string unwind; in ErrorMsg() local
107 unwind += unwinder->FormatFrame(i) + '\n'; in ErrorMsg()
113 function_names.front() + "\n" + "Unwind data:\n" + unwind; in ErrorMsg()
|
| /aosp12/system/unwinding/libunwindstack/ |
| H A D | AndroidVersions.md | 6 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 …]
|
| H A D | Android.bp | 418 name: "unwind",
422 "tools/unwind.cpp",
|
| /aosp12/bionic/docs/ |
| H A D | fdtrack.md | 22 implements a library that uses libunwindstack to unwind and store fd creation backtraces.
45 There are multiple methods to unwind in Android:
50 * Able to unwind through ART
53 statically-linked and steps are taken to prevent the unwind from being
61 * Unable to unwind through ART because it doesn't maintain the frame pointer
|
| H A D | libc_assembler.md | 13 * Verify that unwind information for new routine looks correct. See
14 the [Unwind Info](#unwind-info) section for details about how to verify this.
147 It is also important to verify that the unwind information for these
153 an unwind with incorrect function information.
159 arm32, where it's possible to use ARM specific unwind directives.
163 to verify unwind cases, such as around branches, where unwind information
|
| /aosp12/art/test/137-cfi/src/ |
| H A D | Main.java | 61 unwind(); in compare()
67 public void unwind() { in unwind() method in Main
|
| /aosp12/frameworks/libs/native_bridge_support/libc/ |
| H A D | Android.bp | 88 // Arm 32 bit does not produce complete exidx unwind information
90 // include needed unwind information.
|
| /aosp12/bionic/libc/arch-x86_64/bionic/ |
| H A D | __bionic_clone.S | 61 # We don't want anyone to unwind past this point.
|
| /aosp12/frameworks/compile/mclinker/tools/mcld/ |
| H A D | Options.td | 87 def LDGeneratedUnwindInfo : Flag<["--"], "ld-generated-unwind-info">,
89 … HelpText<"Request creation of unwind info for linker generated code sections like PLT">;
91 def NoLDGeneratedUnwindInfo : Flag<["--"], "no-ld-generated-unwind-info">,
93 … HelpText<"Don't create unwind info for linker generated sections to save size">;
|
| /aosp12/system/extras/simpleperf/doc/ |
| H A D | README.md | 136 3. Can only unwind 64K stack for each sample. So usually can't show complete flamegraph. But
144 stack frame registers. So the kernel can't unwind user stack containing both ARM/THUMB code.
167 a callchain. But the thread stack can be much longer than 64KB. In that case, we can't unwind to
201 The debug information needed to unwind C functions is in .debug_frame section, which is usually
|
| H A D | inferno.md | 78 `simpleperf` to unwind the stack via the kernel and frame pointers. Try to
|
| H A D | executable_commands_reference.md | 68 The debug-unwind command: debug/test dwarf based offline unwinding, used for debugging simpleperf.
|
| /aosp12/system/unwinding/libbacktrace/ |
| H A D | Android.bp | 186 // This forces the creation of eh_frame with unwind information
|
| /aosp12/art/oatdump/ |
| H A D | Android.bp | 155 // defined in libgcc_eh.a(unwind-dw2.o)
|
| /aosp12/art/runtime/ |
| H A D | Android.bp | 41 // Arm 32 bit does not produce complete exidx unwind information
43 // include needed unwind information.
|
| /aosp12/art/dex2oat/ |
| H A D | Android.bp | 392 // defined in libgcc_eh.a(unwind-dw2.o)
|
| /aosp12/bionic/libc/ |
| H A D | Android.bp | 1714 // Arm 32 bit does not produce complete exidx unwind information
1716 // include needed unwind information.
|
| /aosp12/bionic/libc/malloc_debug/ |
| H A D | README.md | 165 that is extra thorough and can unwind through Java frames. This will run
|
| /aosp12/packages/apps/TV/libs/m2/ |
| H A D | javac-shaded-9-dev-r4023-3.jar | org/openjdk/tools/sjavac/server/log/LoggingOutputStream.class
LoggingOutputStream.java
package ... |
| /aosp12/packages/apps/TV/libs/ |
| H A D | google-java-format-1.7-all-deps.jar | META-INF/
META-INF/MANIFEST.MF
com/
com/google/
com/ ... |
| /aosp12/packages/inputmethods/LatinIME/dictionaries/ |
| H A D | en_US_wordlist.combined.gz | 1dictionary=main:en_us,locale=en_US,description=English (US),date ... |
| H A D | en_GB_wordlist.combined.gz | 1dictionary=main:en_gb,locale=en_GB,description=English (UK),date ... |
| H A D | en_wordlist.combined.gz | 1dictionary=main:en,locale=en,description=English,date=1414726273, ... |