diff options
| author | Thiago Jung Bauermann <thiago.bauermann@linaro.org> | 2024-01-23 14:11:33 -0300 |
|---|---|---|
| committer | Thiago Jung Bauermann <thiago.bauermann@linaro.org> | 2024-01-24 11:41:01 -0300 |
| commit | 44acb01769b03fe9d06e953b21b8aed4e0f4261b (patch) | |
| tree | e6ad27e3f91339a78de6691b988e67b939120e73 /gdb/dwarf2/read.c | |
| parent | 8669a8b67408c11d6bf77a09c6aa733f7150abed (diff) | |
| download | gdb-44acb01769b03fe9d06e953b21b8aed4e0f4261b.zip gdb-44acb01769b03fe9d06e953b21b8aed4e0f4261b.tar.gz gdb-44acb01769b03fe9d06e953b21b8aed4e0f4261b.tar.bz2 | |
gdb/arm: Fix epilogue frame id
arm_epilogue_frame_this_id has a comment saying that it fall backs to using
the current PC if the function start address can't be identified, but it
actually uses only the PC to make the frame id.
This patch makes the code match the comment. Another hint that it's what
is intended is that arm_prologue_this_id, a function almost identical to
it, does that.
The problem was found by code inspection. It fixes the following testsuite
failures:
FAIL: gdb.base/unwind-on-each-insn.exp: foo: instruction 9: check frame-id matches
FAIL: gdb.reverse/solib-reverse.exp: reverse-next third shr1
FAIL: gdb.reverse/solib-reverse.exp: reverse-next second shr1
FAIL: gdb.reverse/solib-reverse.exp: reverse-next first shr1
FAIL: gdb.reverse/solib-reverse.exp: reverse-next generic
FAIL: gdb.reverse/solib-reverse.exp: reverse-step into solib function one
FAIL: gdb.reverse/solib-reverse.exp: reverse-step within solib function one
FAIL: gdb.reverse/solib-reverse.exp: reverse-step into solib function two
FAIL: gdb.reverse/solib-reverse.exp: reverse-step within solib function two
Tested on arm-linux-gnueabi-hf.
Diffstat (limited to 'gdb/dwarf2/read.c')
0 files changed, 0 insertions, 0 deletions