diff options
author | Andrew Burgess <aburgess@redhat.com> | 2025-02-06 12:16:48 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2025-02-14 21:06:30 +0000 |
commit | 6ea89e2ddb2af33f1778faeeeb8149a2f575fbd3 (patch) | |
tree | feae67c070a71d02ec8edf73fbb861c2ecb29b62 /gdb/testsuite/gdb.python | |
parent | 9436542558915d5564d05ccb29d1b43a26e37698 (diff) | |
download | binutils-6ea89e2ddb2af33f1778faeeeb8149a2f575fbd3.zip binutils-6ea89e2ddb2af33f1778faeeeb8149a2f575fbd3.tar.gz binutils-6ea89e2ddb2af33f1778faeeeb8149a2f575fbd3.tar.bz2 |
gdb/tui: update maybe_update to take gdbarch
This is a refactor to setup for the next commit.
The maybe_update function currently takes a frame_info_ptr&, however,
it only uses this to get the frame's gdbarch.
In the next commit I want to call maybe_update when I have a gdbarch,
but no frame_info_ptr& (the inferior hasn't even started).
So, update maybe_update to take the gdbarch, and update the callers to
pass that through. Most callers already have the gdbarch to hand, but
in one place I do need to extract this from the frame_info_ptr&.
There should be no user visible changes after this commit.
Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'gdb/testsuite/gdb.python')
0 files changed, 0 insertions, 0 deletions