4cc36d2b43
It turns out that for the dwarf information, if a FDE indicates it's pc relative, then pc has to be incremented by the load bias. If not, then it should not be incremented. Previously, the code always subtracted load bias values from pcs, and assumed that all fdes were incremented by load bias values. The new code actually reads the fdes and adjusted the pcs in the fde and in the eh frame hdr so that load bias values are already handled properly. In addition, add dumping of arm exidx values in unwind_reg_info. This allowed verifying that the debug frame in those elf files was being handled properly. Added a new unit test that only has a debug frame that has a non-zero load bias and has fde entries that do not have pc relative encoding. Fix a couple of other small bugs. Bug: 109824792 Test: All libbacktrace/libunwindstack unit tests pass. Test: Ran ART 137-cfi test and 004-ThreadStress. Test: Verify that displaying the fde start and end pc actually match the Test: real data for fde that have pc relative set, and that don't. Test: Verified that the unwind information for arm exidx matches the Test: debug frame data. Change-Id: I707555286b5cb05df9f25489e8c5ede753cfe0fb |
||
|---|---|---|
| .. | ||
| art_quick_osr_stub_arm | ||
| bad_eh_frame_hdr_arm64 | ||
| debug_frame_first_x86 | ||
| debug_frame_load_bias_arm | ||
| eh_frame_hdr_begin_x86_64 | ||
| gnu_debugdata_arm | ||
| jit_debug_arm | ||
| jit_debug_x86 | ||
| jit_map_arm | ||
| offset_arm | ||
| straddle_arm | ||
| straddle_arm64 | ||