Recently, the maps for an elf in memory might show up looking like: f0000-f1000 0 r-- /system/lib/libc.so f1000-f2000 0 --- f2000-f3000 1000 r-x /system/lib/libc.so f3000-f4000 2000 rw- /system/lib/libc.so The problem is that there is logic in the code that assumed that the map before the execute map must be the read-only map. In the case above, this is not true. Add a new prev_real_map that will point to the previous map that is not one of these empty maps. This will fix the backtraces that look like this: #00 pc 0000000000050d58 /apex/com.android.runtime/lib64/bionic/libc.so!libc.so (offset 0x50000) (syscall+24) (BuildId: 5252408bf30e395d49ee270b54c77ca4) To get rid of the !libc.so and the offset value, which is not correct. Added new unit tests to verify this. Added new offline test which an empty map between read-only and execute map. Before this change, the backtraces had lines like libc.so!libc.so (offset XXX) would be present. Bug: 148075852 Test: Ran unit tests. Change-Id: Ie04bfc96b8f91ed885cb1e655cf1e346efe48a45 |
||
|---|---|---|
| .. | ||
| art_quick_osr_stub_arm | ||
| bad_eh_frame_hdr_arm64 | ||
| debug_frame_first_x86 | ||
| debug_frame_load_bias_arm | ||
| eh_frame_bias_x86 | ||
| eh_frame_hdr_begin_x86_64 | ||
| empty_arm64 | ||
| gnu_debugdata_arm | ||
| invalid_elf_offset_arm | ||
| jit_debug_arm | ||
| jit_debug_x86 | ||
| jit_map_arm | ||
| load_bias_different_section_bias_arm64 | ||
| load_bias_ro_rx_x86_64 | ||
| offset_arm | ||
| shared_lib_in_apk_arm64 | ||
| shared_lib_in_apk_memory_only_arm64 | ||
| shared_lib_in_apk_single_map_arm64 | ||
| signal_load_bias_arm | ||
| straddle_arm | ||
| straddle_arm64 | ||