aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.ada
diff options
context:
space:
mode:
authorJoel Brobecker <brobecker@gnat.com>2006-10-06 20:48:42 +0000
committerJoel Brobecker <brobecker@gnat.com>2006-10-06 20:48:42 +0000
commit390a1bd069f757426ffc8ed1d2662afb12d343ae (patch)
treebaf3a57a76fc4f981767030c1565f79d3644ede6 /gdb/testsuite/gdb.ada
parent714e295ef033e42b85d0f74fe523d3850e5e0fa4 (diff)
downloadgdb-390a1bd069f757426ffc8ed1d2662afb12d343ae.zip
gdb-390a1bd069f757426ffc8ed1d2662afb12d343ae.tar.gz
gdb-390a1bd069f757426ffc8ed1d2662afb12d343ae.tar.bz2
* gdb.ada/arrayidx.exp: Remove calls to setup_kfail now that
the corresponding bug has been fixed in GDB (PR/2018).
Diffstat (limited to 'gdb/testsuite/gdb.ada')
-rw-r--r--gdb/testsuite/gdb.ada/arrayidx.exp18
1 files changed, 0 insertions, 18 deletions
diff --git a/gdb/testsuite/gdb.ada/arrayidx.exp b/gdb/testsuite/gdb.ada/arrayidx.exp
index 051937f..c6cd0d3 100644
--- a/gdb/testsuite/gdb.ada/arrayidx.exp
+++ b/gdb/testsuite/gdb.ada/arrayidx.exp
@@ -49,22 +49,10 @@ gdb_test "print one_two_three" \
"\\(1, 2, 3\\)" \
"print one_two_three, indexes off"
-# There is a bug somewhere that causes the debugger to think that
-# this array is indexed by an integer subrange, which it is actually
-# indexed by an enumerated type. As a consequence, indexes for this
-# array will be printed using their underlying integer value instead
-# of their names. Also, even when printing this array without indexes,
-# because the underlying value of the first enumeration is zero, the
-# debugger ends up printing this index even when "array-indexes" are
-# off, just because the index of the first element is not an enumerated
-# type, and its value is not one.
-setup_kfail "*-*-*" gdb/2018
gdb_test "print e_one_two_three" \
"\\(1, 2, 3\\)" \
"print e_one_two_three, indexes off"
-# Same as when printing e_one_two_three above.
-setup_kfail "*-*-*" gdb/2018
gdb_test "print r_two_three" \
"\\(two => 2, 3\\)" \
"print r_two_three, indexes off"
@@ -99,16 +87,10 @@ gdb_test "print one_two_three" \
"\\(1 => 1, 2 => 2, 3 => 3\\)" \
"print one_two_three"
-# Same as first attempt at printing this array, we currently fail.
-# See details above.
-setup_kfail "*-*-*" gdb/2018
gdb_test "print e_one_two_three" \
"\\(one => 1, two => 2, three => 3\\)" \
"print e_one_two_three"
-# Same as first attempt at printing this array, we currently fail.
-# See details above.
-setup_kfail "*-*-*" gdb/2018
gdb_test "print r_two_three" \
"\\(two => 2, three => 3\\)" \
"print r_two_three"