aboutsummaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2011-07-01 18:27:12 +0000
committerJoel Brobecker <brobecker@gnat.com>2011-07-01 18:27:12 +0000
commit54ae186fb505f4873858ae56b2298c9471f9eaee (patch)
tree85b515d6e0cd7dc91d49fd61a67fda2ab27a73bb /MAINTAINERS
parent8f17729f21e54827ba8de614be382c4fbd6b690f (diff)
downloadgdb-54ae186fb505f4873858ae56b2298c9471f9eaee.zip
gdb-54ae186fb505f4873858ae56b2298c9471f9eaee.tar.gz
gdb-54ae186fb505f4873858ae56b2298c9471f9eaee.tar.bz2
Fix ada array bounds display
Array bounds were not correctly displayed when the SHOW parameter of print_type functions is set to -1. This shows up in the following type of situation, where we have a declaration as follow: Anon_Array_Int_Obj : array (1..10) of Integer := (others => 8); In GDB/MI mode, trying to print the type info for our array object yields: (gdb) -var-create ai 0 Anon_Array_Int_Obj (gdb) -var-info-type ai ^done,type="array (...) of integer" The actual bounds are missing. Contrast this with what happens when in GDB/CLI mode: (gdb) ptype Anon_Array_Int_Obj type = array (1 .. 10) of integer This patch fixes array type printing accordingly. And as it turns out, it also improves the output for one of the tests already present, so it shows that it's not just the GDB/MI mode that's affected. gdb/ChangeLog (Jean-Charles Delay): * ada-typeprint.c (print_array_type): removed if condition on show being negative for bounds printing. gdb/testsuite/ChangeLog (Jean-Charles Delay): * gdb.ada/packed_array.exp: fixed expected output.
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions