gdb: use inferior parameter in add_vsyscall_page

Use the new inferior parameter instead of target_gdbarch.  There are
still hidden references to the current context behind core_bfd and
exec_bfd, but this seemed better than nothing.

gdb/ChangeLog:

	* symfile-mem.c (add_vsyscall_page): Use inferior parameter
	instead of target_gdbarch.

Change-Id: Iaf5ace555ee8e46cbef5190aca1f6fe639f06677
This commit is contained in:
Simon Marchi 2020-10-24 23:00:10 -04:00
parent 324956617c
commit c75e31a1ec
2 changed files with 7 additions and 1 deletions

View File

@ -1,3 +1,8 @@
2020-10-24 Simon Marchi <simon.marchi@polymtl.ca>
* symfile-mem.c (add_vsyscall_page): Use inferior parameter
instead of target_gdbarch.
2020-10-24 Simon Marchi <simon.marchi@polymtl.ca>
* jit.c (jit_reader_load_command): Pass current inferior.

View File

@ -53,6 +53,7 @@
#include "auxv.h"
#include "elf/common.h"
#include "gdb_bfd.h"
#include "inferior.h"
/* Verify parameters of target_read_memory_bfd and target_read_memory are
compatible. */
@ -161,7 +162,7 @@ add_vsyscall_page (inferior *inf)
{
struct mem_range vsyscall_range;
if (gdbarch_vsyscall_range (target_gdbarch (), &vsyscall_range))
if (gdbarch_vsyscall_range (inf->gdbarch, &vsyscall_range))
{
struct bfd *bfd;