diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2023-09-29 14:24:38 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2023-10-10 10:44:35 -0400 |
| commit | 99d9c3b92ca96a7425cbb6b1bf453ede9477a2ee (patch) | |
| tree | 7f642c989f7c7b49bd40ab5873fc12be632e6ea9 /gdb/fbsd-nat.c | |
| parent | 72c4529c85907a5e1e04960ff1362a5a185553a0 (diff) | |
| download | gdb-99d9c3b92ca96a7425cbb6b1bf453ede9477a2ee.zip gdb-99d9c3b92ca96a7425cbb6b1bf453ede9477a2ee.tar.gz gdb-99d9c3b92ca96a7425cbb6b1bf453ede9477a2ee.tar.bz2 | |
gdb: remove target_gdbarch
This function is just a wrapper around the current inferior's gdbarch.
I find that having that wrapper just obscures where the arch is coming
from, and that it's often used as "I don't know which arch to use so
I'll use this magical target_gdbarch function that gets me an arch" when
the arch should in fact come from something in the context (a thread,
objfile, symbol, etc). I think that removing it and inlining
`current_inferior ()->arch ()` everywhere will make it a bit clearer
where that arch comes from and will trigger people into reflecting
whether this is the right place to get the arch or not.
Change-Id: I79f14b4e4934c88f91ca3a3155f5fc3ea2fadf6b
Reviewed-By: John Baldwin <jhb@FreeBSD.org>
Approved-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'gdb/fbsd-nat.c')
| -rw-r--r-- | gdb/fbsd-nat.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/fbsd-nat.c b/gdb/fbsd-nat.c index 55a36f2..0e0d0cd 100644 --- a/gdb/fbsd-nat.c +++ b/gdb/fbsd-nat.c @@ -178,7 +178,7 @@ fbsd_nat_target::find_memory_regions (find_memory_region_ftype func, { gdb_printf ("Save segment, %ld bytes at %s (%c%c%c)\n", (long) size, - paddress (target_gdbarch (), kve->kve_start), + paddress (current_inferior ()->arch (), kve->kve_start), kve->kve_protection & KVME_PROT_READ ? 'r' : '-', kve->kve_protection & KVME_PROT_WRITE ? 'w' : '-', kve->kve_protection & KVME_PROT_EXEC ? 'x' : '-'); |