public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/27787] FAIL: gdb.python/flexible-array-member.exp: python print(zs['items'].type.range())
Date: Fri, 30 Apr 2021 09:42:38 +0000 [thread overview]
Message-ID: <bug-27787-4717-oSe17ohQiI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27787-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27787
--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Simon Marchi from comment #3)
> (In reply to Tom de Vries from comment #2)
> > (In reply to Simon Marchi from comment #1)
> > > Which compiler? I presume this is very debug-info sensitive.
> >
> > Fails with gcc 7.5.0 and 8.4.0.
> >
> > Passes with gcc 9.3.1, 10.3.0 and 11.0.1.
>
> Thanks, I'll try it soon. I am guessing that we'll just get different
> values, and that we'll end up changing the regexp to accept these values too.
I compared 8.4.0 and 9.3.1, and found a difference in debug info.
In case of 8.4.0, we have variable zs:
...
<1><1f0>: Abbrev Number: 9 (DW_TAG_variable)
<1f1> DW_AT_name : zs
...
<1f7> DW_AT_type : <0x205>
...
with type:
...
<1><205>: Abbrev Number: 10 (DW_TAG_pointer_type)
<206> DW_AT_byte_size : 8
<207> DW_AT_type : <0x176>
...
pointing to struct type:
...
<1><176>: Abbrev Number: 4 (DW_TAG_structure_type)
<177> DW_AT_name : zero_size
...
with member:
...
<2><18e>: Abbrev Number: 6 (DW_TAG_member)
<18f> DW_AT_name : items
<196> DW_AT_type : <0x19c>
...
with type:
...
<1><19c>: Abbrev Number: 7 (DW_TAG_array_type)
<19d> DW_AT_type : <0xfb>
<1a1> DW_AT_sibling : <0x1ab>
<2><1a5>: Abbrev Number: 8 (DW_TAG_subrange_type)
<1a6> DW_AT_type : <0xf4>
<2><1aa>: Abbrev Number: 0
...
The same for 9.3.1, but with DW_AT_count 0 in the subrange:
...
<1><19c>: Abbrev Number: 7 (DW_TAG_array_type)
<19d> DW_AT_type : <0xfb>
<1a1> DW_AT_sibling : <0x1ac>
<2><1a5>: Abbrev Number: 9 (DW_TAG_subrange_type)
<1a6> DW_AT_type : <0xf4>
<1aa> DW_AT_count : 0
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-30 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 18:22 [Bug testsuite/27787] New: " vries at gcc dot gnu.org
2021-04-28 19:23 ` [Bug testsuite/27787] " simark at simark dot ca
2021-04-28 19:32 ` vries at gcc dot gnu.org
2021-04-28 20:45 ` simark at simark dot ca
2021-04-30 9:42 ` vries at gcc dot gnu.org [this message]
2021-04-30 13:15 ` simark at simark dot ca
2021-05-04 9:22 ` vries at gcc dot gnu.org
2021-05-04 15:28 ` simark at simark dot ca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27787-4717-oSe17ohQiI@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).