aboutsummaryrefslogtreecommitdiff
path: root/gdb/rust-lang.c
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2019-02-16 17:26:44 +0000
committerAndrew Burgess <andrew.burgess@embecosm.com>2019-04-30 10:34:26 +0100
commitbf7a4de1722a63c8b017d010e75d5e9e5e622f36 (patch)
tree82ae4065b73b0aa1ba90f21e2369234f48468a67 /gdb/rust-lang.c
parentbbe75b9d00cc6f0694ff26569505c349d55e35f1 (diff)
downloadbinutils-bf7a4de1722a63c8b017d010e75d5e9e5e622f36.zip
binutils-bf7a4de1722a63c8b017d010e75d5e9e5e622f36.tar.gz
binutils-bf7a4de1722a63c8b017d010e75d5e9e5e622f36.tar.bz2
gdb/fortran: print function arguments when printing function type
Before this commit using ptype on a Fortran function will include information about the functions return type, but not the expected arguments as it would for C or C++. After this commit argument types are included in the ptype output. For example, before GDB prints: (gdb) ptype fun1 type = integer(kind=4) () (gdb) ptype is_bigger type = logical(kind=4) () and after GDB prints: (gdb) ptype fun1 type = integer(kind=4) (integer(kind=4)) (gdb) ptype is_bigger type = logical(kind=4) (integer(kind=4), integer(kind=4)) gdb/ChangeLog: * f-typeprint.c (f_type_print_varspec_suffix): Handle printing function arguments. gdb/testsuite/ChangeLog: * gdb.fortran/ptype-on-functions.exp: New file. * gdb.fortran/ptype-on-functions.f90: New file.
Diffstat (limited to 'gdb/rust-lang.c')
0 files changed, 0 insertions, 0 deletions