diff options
| author | Simon Marchi <simon.marchi@efficios.com> | 2023-10-02 14:46:18 -0400 |
|---|---|---|
| committer | Simon Marchi <simon.marchi@efficios.com> | 2023-10-19 10:57:51 -0400 |
| commit | 581b34c2a153d36876ec92bbcd1820ac1d99f83b (patch) | |
| tree | c79693a31eab84dea680b98c942ab307a996ab60 /gdb/solib-frv.c | |
| parent | 6fe4d5bf18512798b3a685599bfcff5aab3f798e (diff) | |
| download | fsf-binutils-gdb-581b34c2a153d36876ec92bbcd1820ac1d99f83b.zip fsf-binutils-gdb-581b34c2a153d36876ec92bbcd1820ac1d99f83b.tar.gz fsf-binutils-gdb-581b34c2a153d36876ec92bbcd1820ac1d99f83b.tar.bz2 | |
gdb: add program_space parameter to target_so_ops::clear_solib
The clear_solib is implicitly meant to clear the resources associated to
the current program space (that's what the solib implementations that
actually support multi-program-space / multi-inferior do). Make that
explicit by adding a program_space parameter and pass down
current_program_space in call sites. The implementation of the
clear_solib callbacks is fairly simple, I don't think any of them rely
on global state other than accessing current_program_space.
Change-Id: I8d0cc4db7b4f8db8d7452879c0c62db03269bf46
Approved-By: Pedro Alves <pedro@palves.net>
Reviewed-By: Reviewed-By: Lancelot Six <lancelot.six@amd.com>
Diffstat (limited to 'gdb/solib-frv.c')
| -rw-r--r-- | gdb/solib-frv.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/solib-frv.c b/gdb/solib-frv.c index d4e84a1..c61ed79 100644 --- a/gdb/solib-frv.c +++ b/gdb/solib-frv.c @@ -806,7 +806,7 @@ frv_solib_create_inferior_hook (int from_tty) } static void -frv_clear_solib (void) +frv_clear_solib (program_space *pspace) { lm_base_cache = 0; enable_break2_done = 0; |