diff options
author | Andrew Burgess <aburgess@redhat.com> | 2025-08-21 12:58:30 +0100 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2025-08-26 21:48:34 +0100 |
commit | 2bd87cef85034dbf39a2817fba4f03828c0ca782 (patch) | |
tree | 4275d2a6611dfcbbcf8552916f58cc74c93b0dd4 /r | |
parent | e3a6f62033cd3a1acdafc34d8bf7e22e532dff9b (diff) | |
download | binutils-2bd87cef85034dbf39a2817fba4f03828c0ca782.zip binutils-2bd87cef85034dbf39a2817fba4f03828c0ca782.tar.gz binutils-2bd87cef85034dbf39a2817fba4f03828c0ca782.tar.bz2 |
gdb: use current_program_space->core_bfd() a little less
The function linux_read_core_file_mappings is passed an argument CBFD,
which is the BFD for the core file. In
core_target::build_file_mappings, where the function is called, we
pass current_program_space->core_bfd() as the argument.
However, in linux_read_core_file_mappings, in some places we use the
CBFD argument, and in other places we directly use
current_program_space->core_bfd(). This is confusing, and
unnecessary. Lets not do that.
Standardise on just using CBFD. This removes some references to
global state in favour of passing the global state in as an argument,
I think this is a good thing.
There should be no user visible changes after this commit.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'r')
0 files changed, 0 insertions, 0 deletions