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] New: FAIL: gdb.python/flexible-array-member.exp: python print(zs['items'].type.range())
Date: Wed, 28 Apr 2021 18:22:26 +0000	[thread overview]
Message-ID: <bug-27787-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=27787

            Bug ID: 27787
           Summary: FAIL: gdb.python/flexible-array-member.exp: python
                    print(zs['items'].type.range())
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

...
FAIL: gdb.python/flexible-array-member.exp: python
print(zs['items'].type.range())
FAIL: gdb.python/flexible-array-member.exp: python
print(zso['items'].type.range())
...

First in more detail:
...
(gdb) FAIL: gdb.python/flexible-array-member.exp: python
print(zs['items'].type.range())
python print(zso['items'].type.range())^M
(0, 0)^M
...

Related test-case portion:
...
# Verify the range attribute.  It looks a bit inconsistent that the high bound  
# is sometimes 0, sometimes -1, but that's what GDB produces today, so that's   
# what we test.                                                                 

gdb_test "python print(ns\['items'\].type.range())" "\\(0, 0\\)"
gdb_test "python print(zs\['items'\].type.range())" "\\(0, -1\\)"
gdb_test "python print(zso\['items'\].type.range())" "\\(0, -1\\)"
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-04-28 18:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 18:22 vries at gcc dot gnu.org [this message]
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
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@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).