diff options
author | Simon Marchi <simon.marchi@efficios.com> | 2023-12-21 16:32:55 +0000 |
---|---|---|
committer | Simon Marchi <simon.marchi@polymtl.ca> | 2023-12-24 09:02:08 -0500 |
commit | 306f960b492b35798e01acef5e177838bffc362d (patch) | |
tree | f3aaef324c5b24684166e877e495b91f5ee6d254 /gdb/python/py-unwind.c | |
parent | c465f4303776f6609f1ca4835b4bf3627e7c61af (diff) | |
download | fsf-binutils-gdb-306f960b492b35798e01acef5e177838bffc362d.zip fsf-binutils-gdb-306f960b492b35798e01acef5e177838bffc362d.tar.gz fsf-binutils-gdb-306f960b492b35798e01acef5e177838bffc362d.tar.bz2 |
gdb: implement address_from_register using value_from_register
As explained in the comment removed by the previous commit "gdb: pass
non-nullptr frame to gdbarch_value_from_register in
address_from_register", address_from_register copies some implementation
bits from value_from_register:
/* This routine may be called during early unwinding, at a time
where the ID of FRAME is not yet known. Calling value_from_register
would therefore abort in get_frame_id. However, since we only need
a temporary value that is never used as lvalue, we actually do not
really need to set its VALUE_NEXT_FRAME_ID. Therefore, we re-implement
the core of value_from_register, but use the null_frame_id. */
This is no longer relevant, since we now create a value with a valid next
frame id, so change address_from_register to use value_from_register.
Change-Id: I189bd96f28735ed9f47750ffd73764c459ec6f43
Diffstat (limited to 'gdb/python/py-unwind.c')
0 files changed, 0 insertions, 0 deletions