summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2022-08-08 09:56:47 -0600
committerTom Tromey <tromey@adacore.com>2022-08-08 10:00:57 -0600
commitce81f9d6fa885a3faa41613debc8771304dc469b (patch)
tree64a09a47e85c4d07c7719c29c9cec0f31d6adfc3
parente441b55e94c905c6ee4417be3e5d88021d9c5aa6 (diff)
The gdbarch registry patch introduced a regression that could cause a crash when opening files in gdb. The bug is that, previously, the solib ops would default to current_target_so_ops; but the patch changed this code to default to nullptr. This patch fixes the bug by reintroducing the earlier behavior. This is PR gdb/29449. I managed to reproduce the bug with a riscv-elf build and then verified that this fixes the problem. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29449
-rw-r--r--gdb/solib.c8
1 files changed, 7 insertions, 1 deletions
diff --git a/gdb/solib.c b/gdb/solib.c
index d889673dab..25adf586a0 100644
--- a/gdb/solib.c
+++ b/gdb/solib.c
@@ -64,7 +64,13 @@ static const registry<gdbarch>::key<const struct target_so_ops,
static const struct target_so_ops *
solib_ops (struct gdbarch *gdbarch)
{
- return solib_data.get (gdbarch);
+ const struct target_so_ops *result = solib_data.get (gdbarch);
+ if (result == nullptr)
+ {
+ result = current_target_so_ops;
+ set_solib_ops (gdbarch, current_target_so_ops);
+ }
+ return result;
}
/* Set the solib operations for GDBARCH to NEW_OPS. */