diff options
author | Tom Tromey <tromey@adacore.com> | 2021-03-15 06:23:12 -0600 |
---|---|---|
committer | Tom Tromey <tromey@adacore.com> | 2021-03-15 06:23:13 -0600 |
commit | 9863c3b5fc64eec400ed55792a49c678927a6145 (patch) | |
tree | 9d97ec4c7dac8cc8960d66e6ddbac89f15e4cc94 /libiberty/setenv.c | |
parent | 1ac7452264fee536b0f62610e8dbe9f9e253a6f8 (diff) | |
download | fsf-binutils-gdb-9863c3b5fc64eec400ed55792a49c678927a6145.zip fsf-binutils-gdb-9863c3b5fc64eec400ed55792a49c678927a6145.tar.gz fsf-binutils-gdb-9863c3b5fc64eec400ed55792a49c678927a6145.tar.bz2 |
Fix regression in Ada ptype
This fixes PR ada/27545, which points out that a test in
gdb.ada/tagged.exp started failing due to the expression rewrite. I
didn't notice this failure because my system gcc-gnat debuginfo was
out of date, and so the test was already failing in the baseline.
Previously, the OP_VAR_VALUE case in ada_evaluate_subexp ended up
doing a recursive call:
arg1 = evaluate_subexp (nullptr, exp, pos, EVAL_NORMAL);
However, during the rewrite I missed this fact and had the new code
call the superclass implementation.
This patch fixes the bug by changing this code to use a recursive call
instead.
gdb/ChangeLog
2021-03-15 Tom Tromey <tromey@adacore.com>
PR ada/27545:
* ada-lang.c (ada_var_value_operation::evaluate): Use recursive
call for tagged type.
Diffstat (limited to 'libiberty/setenv.c')
0 files changed, 0 insertions, 0 deletions