gdb.dwarf2/data-loc.exp: Remove second DW_AT_upper bound in array range.

The testcase generates an assembly file where a second DW_AT_upper_bound
attribute gets generated in the array range.  This was definitely
unintentional, and I only noticed this after pushing the testcase,
when dumping one more time the DWARF data using readelf.

This patch fixes it.

gdb/testsuite/ChangeLog:

        * gdb.dwarf2/data-loc.exp: Remove second DW_AT_upper bound
        attribute in array range.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index a90d85e..b9197ad 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,5 +1,10 @@
 2014-08-18  Joel Brobecker  <brobecker@adacore.com>
 
+       * gdb.dwarf2/data-loc.exp: Remove second DW_AT_upper bound
+       attribute in array range.
+
+2014-08-18  Joel Brobecker  <brobecker@adacore.com>
+
        * gdb.dwarf2/data-loc.c, gdb.dwarf2/data-loc.exp: New files.
 
 2014-08-15  Siva Chandra Reddy  <sivachandra@google.com>

diff --git a/gdb/testsuite/gdb.dwarf2/data-loc.exp b/gdb/testsuite/gdb.dwarf2/data-loc.exp
index 859962a..b5c5f67 100644 (file)
--- a/gdb/testsuite/gdb.dwarf2/data-loc.exp
+++ b/gdb/testsuite/gdb.dwarf2/data-loc.exp
@@ -74,7 +74,6 @@ Dwarf::assemble $asm_file {
                         DW_OP_plus_uconst [get_sizeof "int" 4]
                         DW_OP_deref_size [get_sizeof "int" 4]
                     } SPECIAL_expr}
-                   {DW_AT_upper_bound 5 DW_FORM_data1}
                }
            }
             DW_TAG_typedef {