diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2024-01-11 11:41:04 -0500 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2024-01-11 13:11:19 -0500 |
| commit | 47ff07a6c283a39fa3b8c92d823c8851678dfc0f (patch) | |
| tree | 6197067697917b5a2a6685c66ce9d961d270296f /gdb/python/py-membuf.c | |
| parent | fa87f8e1958b8937047e3d5fcfd8c265745710ae (diff) | |
| download | binutils-47ff07a6c283a39fa3b8c92d823c8851678dfc0f.zip binutils-47ff07a6c283a39fa3b8c92d823c8851678dfc0f.tar.gz binutils-47ff07a6c283a39fa3b8c92d823c8851678dfc0f.tar.bz2 | |
gdb: fix frame passed to gdbarch_value_to_register in value_assign
Commit 78f2fd84e83 ("gdb: remove VALUE_REGNUM, add value::regnum")
introduced an unexpected change in value_assign. It replaced
`get_prev_frame_always (next_frame)` with `next_frame`in the call to
gdbarch_value_to_register.
This is the result of a merge error, since I previously had a patch to
change gdbarch_value_to_register to take the next frame, and later
decided to drop it. Revert that change.
Add a test based on the DWARF assembler to expose the problem and test
the fix. I also tested on ppc64le to make sure the problem reported in
PR 31231 was fixed.
Change-Id: Ib8b851287ac27a4b2e386f7b680cf65865e6aee6
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31231
Diffstat (limited to 'gdb/python/py-membuf.c')
0 files changed, 0 insertions, 0 deletions