aboutsummaryrefslogtreecommitdiff
path: root/gdb/frame.c
diff options
context:
space:
mode:
authorKevin Buettner <kevinb@redhat.com>2016-09-27 22:45:19 -0700
committerKevin Buettner <kevinb@redhat.com>2016-11-16 11:38:44 -0700
commit33cc7d368f420326606695daafd6292e2779c6af (patch)
treed695614addf8e1c850faad0b5c9bd5d2f8addc60 /gdb/frame.c
parent41b56feb5063aee4fefb4a991eb796d1e8a7475e (diff)
downloadgdb-33cc7d368f420326606695daafd6292e2779c6af.zip
gdb-33cc7d368f420326606695daafd6292e2779c6af.tar.gz
gdb-33cc7d368f420326606695daafd6292e2779c6af.tar.bz2
Make gdb.PendingFrame.read_register handle "user" registers.
The C function, pending_framepy_read_register(), which implements the python interface gdb.PendingFrame.read_register does not handle the so called "user" registers like "pc". An assertion error is triggered due to the user registers having numbers larger than or equal to gdbarch_num_regs(gdbarch). With the VALUE_FRAME_ID tweak in place, the call to get_frame_register_value() can simply be replaced by a call to value_of_register(), which handles both real registers as well as the user registers. gdb/ChangeLog: * python/py-unwind.c (pending_framepy_read_register): Use value_of_register() instead of get_frame_register_value().
Diffstat (limited to 'gdb/frame.c')
0 files changed, 0 insertions, 0 deletions