bc3c0632a2
When evaluating and expression containing UNOP_IND in mode EVAL_AVOID_SIDE_EFFECTS, GDB currently (mostly) returns the result of a call to value_zero meaning we get back an object with the correct type, but its contents are all zero. If the target type contains fields with dynamic type then in order to resolve these dynamic fields GDB will need to read the value of the field from within the parent object. In this case the field value will be zero as a result of the call to value_zero mentioned above. The idea behind EVAL_AVOID_SIDE_EFFECTS is to avoid the chance that doing something like `ptype` will modify state within the target, for example consider: ptype i++. However, there is already precedence within GDB that sometimes, in order to get accurate type results, we can't avoid reading from the target, even when EVAL_AVOID_SIDE_EFFECTS is in effect. For example I would point to eval.c:evaluate_var_value, the handling of OP_REGISTER, the handling of value_x_unop in many places. I believe the Ada expression evaluator also ignore EVAL_AVOID_SIDE_EFFECTS in some cases. I am therefor proposing that, in the case where a pointer points at a dynamic type, we allow UNOP_IND to perform the actual indirection. This allows accurate types to be displayed in more cases. gdb/ChangeLog: * eval.c (evaluate_subexp_standard): Call value_ind for points to dynamic types in UNOP_IND. gdb/testsuite/ChangeLog: * gdb.fortran/pointer-to-pointer.exp: Additional tests.
58 lines
1.9 KiB
Text
58 lines
1.9 KiB
Text
# Copyright 2020-2021 Free Software Foundation, Inc.
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/> .
|
|
|
|
# Test for GDB printing a pointer to a type containing a buffer.
|
|
|
|
if {[skip_fortran_tests]} { return -1 }
|
|
|
|
standard_testfile ".f90"
|
|
load_lib fortran.exp
|
|
|
|
if {[prepare_for_testing ${testfile}.exp ${testfile} ${srcfile} \
|
|
{debug f90}]} {
|
|
return -1
|
|
}
|
|
|
|
if ![fortran_runto_main] {
|
|
untested "could not run to main"
|
|
return -1
|
|
}
|
|
|
|
# Depending on the compiler being used, the type names can be printed
|
|
# differently.
|
|
set real4 [fortran_real4]
|
|
|
|
gdb_breakpoint [gdb_get_line_number "Break Here"]
|
|
gdb_continue_to_breakpoint "Break Here"
|
|
|
|
gdb_test "print buffer" \
|
|
" = \\(PTR TO -> \\( Type l_buffer \\)\\) $hex"
|
|
gdb_test "ptype buffer" \
|
|
[multi_line \
|
|
"type = PTR TO -> \\( Type l_buffer" \
|
|
" $real4 :: alpha\\(:\\)" \
|
|
"End Type l_buffer \\)" ]
|
|
gdb_test "ptype buffer%alpha" "type = $real4 \\(5\\)"
|
|
|
|
# GDB allows pointer types to be dereferenced using '*'. This is not
|
|
# real Fortran syntax, just something extra that GDB supports.
|
|
gdb_test "print *buffer" \
|
|
" = \\( alpha = \\(1\\.5, 2\\.5, 3\\.5, 4\\.5, 5\\.5\\) \\)"
|
|
gdb_test "ptype *buffer" \
|
|
[multi_line \
|
|
"type = Type l_buffer" \
|
|
" $real4 :: alpha\\(5\\)" \
|
|
"End Type l_buffer" ]
|
|
gdb_test "ptype (*buffer)%alpha" "type = $real4 \\(5\\)"
|