Blame SOURCES/gdb-flexible-array-member-expected-pattern.patch

4416f5
From FEDORA_PATCHES Mon Sep 17 00:00:00 2001
4416f5
From: Simon Marchi <simon.marchi@efficios.com>
4416f5
Date: Tue, 4 May 2021 11:20:09 -0400
4416f5
Subject: gdb-flexible-array-member-expected-pattern.patch
4416f5
4416f5
;; Backport "adjust gdb.python/flexible-array-member.exp expected pattern"
4416f5
;; (Simon Marchi)
4416f5
4416f5
The `Type.range ()` tests in gdb.python/flexible-array-member.exp pass
4416f5
when the test is compiled with gcc 9 or later, but not with gcc 8 or
4416f5
earlier:
4416f5
4416f5
    $ make check TESTS="gdb.python/flexible-array-member.exp" RUNTESTFLAGS="CC_FOR_TARGET='gcc-8'"
4416f5
4416f5
    python print(zs['items'].type.range())^M
4416f5
    (0, 0)^M
4416f5
    (gdb) FAIL: gdb.python/flexible-array-member.exp: python print(zs['items'].type.range())
4416f5
    python print(zso['items'].type.range())^M
4416f5
    (0, 0)^M
4416f5
    (gdb) FAIL: gdb.python/flexible-array-member.exp: python print(zso['items'].type.range())
4416f5
4416f5
The value that we get for the upper bound of a flexible array member
4416f5
declared with a "0" size is 0 with gcc <= 8 and is -1 for gcc >= 9.
4416f5
This is due to different debug info.  For this member, gcc 8 does:
4416f5
4416f5
    0x000000d5:   DW_TAG_array_type
4416f5
                    DW_AT_type [DW_FORM_ref4]       (0x00000034 "int")
4416f5
                    DW_AT_sibling [DW_FORM_ref4]    (0x000000e4)
4416f5
4416f5
    0x000000de:     DW_TAG_subrange_type
4416f5
                      DW_AT_type [DW_FORM_ref4]     (0x0000002d "long unsigned int")
4416f5
4416f5
For the same type, gcc 9 does:
4416f5
4416f5
    0x000000d5:   DW_TAG_array_type
4416f5
                    DW_AT_type [DW_FORM_ref4]       (0x00000034 "int")
4416f5
                    DW_AT_sibling [DW_FORM_ref4]    (0x000000e5)
4416f5
4416f5
    0x000000de:     DW_TAG_subrange_type
4416f5
                      DW_AT_type [DW_FORM_ref4]     (0x0000002d "long unsigned int")
4416f5
                      DW_AT_count [DW_FORM_data1]   (0x00)
4416f5
4416f5
Ideally, GDB would present a consistent and documented value for an
4416f5
array member declared with size 0, regardless of how the debug info
4416f5
looks like.  But for now, just change the test to accept the two
4416f5
values, to get rid of the failure and make the test in sync
4416f5
4416f5
I also realized (by looking at the py-type.exp test) that calling the
4416f5
fields method on an array type yields one field representing the "index"
4416f5
of the array.  The type of that field is of type range
4416f5
(gdb.TYPE_CODE_RANGE).  When calling `.range()` on that range type, it
4416f5
yields the same range tuple as when calling `.range()` on the array type
4416f5
itself.  For completeness, add some tests to access the range tuple
4416f5
through that range type as well.
4416f5
4416f5
gdb/testsuite/ChangeLog:
4416f5
4416f5
	* gdb.python/flexible-array-member.exp: Adjust expected range
4416f5
	value for member declared with 0 size.  Test accessing range
4416f5
	tuple through range type.
4416f5
4416f5
Change-Id: Ie4e06d99fe9315527f04577888f48284d649ca4c
4416f5
4416f5
diff --git a/gdb/testsuite/gdb.python/flexible-array-member.exp b/gdb/testsuite/gdb.python/flexible-array-member.exp
4416f5
--- a/gdb/testsuite/gdb.python/flexible-array-member.exp
4416f5
+++ b/gdb/testsuite/gdb.python/flexible-array-member.exp
4416f5
@@ -76,9 +76,17 @@ gdb_test "python print(zso\['items'\] == zso\['items'\]\[0\].address)" "True"
4416f5
 gdb_test "python print(zso\['items'\]\[0\].address + 1 == zso\['items'\]\[1\].address)" "True"
4416f5
 
4416f5
 # Verify the range attribute.  It looks a bit inconsistent that the high bound
4416f5
-# is sometimes 0, sometimes -1, but that's what GDB produces today, so that's
4416f5
-# what we test.
4416f5
+# is sometimes 0, sometimes -1.  It depends on the way the flexible array
4416f5
+# member is specified and on the compiler version (the debug info is
4416f5
+# different).  But that's what GDB produces today, so that's what we test.
4416f5
 
4416f5
 gdb_test "python print(ns\['items'\].type.range())" "\\(0, 0\\)"
4416f5
-gdb_test "python print(zs\['items'\].type.range())" "\\(0, -1\\)"
4416f5
-gdb_test "python print(zso\['items'\].type.range())" "\\(0, -1\\)"
4416f5
+gdb_test "python print(zs\['items'\].type.range())" "\\(0, (0|-1)\\)"
4416f5
+gdb_test "python print(zso\['items'\].type.range())" "\\(0, (0|-1)\\)"
4416f5
+
4416f5
+# Test the same thing, but going explicitly through the array index's range
4416f5
+# type.
4416f5
+
4416f5
+gdb_test "python print(ns\['items'\].type.fields()\[0\].type.range())" "\\(0, 0\\)"
4416f5
+gdb_test "python print(zs\['items'\].type.fields()\[0\].type.range())" "\\(0, (0|-1)\\)"
4416f5
+gdb_test "python print(zso\['items'\].type.fields()\[0\].type.range())" "\\(0, (0|-1)\\)"