aboutsummaryrefslogtreecommitdiff
path: root/gdb/stack.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2022-09-07 08:39:52 -0600
committerTom Tromey <tromey@adacore.com>2023-01-03 08:45:00 -0700
commit4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8 (patch)
treec5b684d3cad8e726247e58566b9d293ece12b756 /gdb/stack.c
parent862ebb27bbe30768356776a10827dd1c0824d405 (diff)
downloadfsf-binutils-gdb-4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8.zip
fsf-binutils-gdb-4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8.tar.gz
fsf-binutils-gdb-4e1d2f5814b29048d1dd1cea2cb50570e6c8f1f8.tar.bz2
Add new overload of gdbarch_return_value
The gdbarch "return_value" can't correctly handle variably-sized types. The problem here is that the TYPE_LENGTH of such a type is 0, until the type is resolved, which requires reading memory. However, gdbarch_return_value only accepts a buffer as an out parameter. Fixing this requires letting the implementation of the gdbarch method resolve the type and return a value -- that is, both the contents and the new type. After an attempt at this, I realized I wouldn't be able to correctly update all implementations (there are ~80) of this method. So, instead, this patch adds a new method that falls back to the current method, and it updates gdb to only call the new method. This way it's possible to incrementally convert the architectures that I am able to test.
Diffstat (limited to 'gdb/stack.c')
-rw-r--r--gdb/stack.c7
1 files changed, 4 insertions, 3 deletions
diff --git a/gdb/stack.c b/gdb/stack.c
index 7f7478e..0fd7978 100644
--- a/gdb/stack.c
+++ b/gdb/stack.c
@@ -2838,9 +2838,10 @@ return_command (const char *retval_exp, int from_tty)
gdb_assert (rv_conv != RETURN_VALUE_STRUCT_CONVENTION
&& rv_conv != RETURN_VALUE_ABI_RETURNS_ADDRESS);
- gdbarch_return_value (cache_arch, function, return_type,
- get_current_regcache (), NULL /*read*/,
- value_contents (return_value).data () /*write*/);
+ gdbarch_return_value_as_value
+ (cache_arch, function, return_type,
+ get_current_regcache (), NULL /*read*/,
+ value_contents (return_value).data () /*write*/);
}
/* If we are at the end of a call dummy now, pop the dummy frame