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 ada/30726] New: [gdb/ada, cc-with-dwz] FAIL: gdb.ada/arr_acc_idx_w_gap.exp: enum_rep
Date: Sun, 06 Aug 2023 13:06:20 +0000	[thread overview]
Message-ID: <bug-30726-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30726
           Summary: [gdb/ada, cc-with-dwz] FAIL:
                    gdb.ada/arr_acc_idx_w_gap.exp: enum_rep
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ada
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

When running with target board cc-with-dwz, I run into:
...
(gdb) print enum_with_gaps'enum_rep(lit3)^M
'Enum_Rep requires argument to have same type as enum^M
(gdb) FAIL: gdb.ada/arr_acc_idx_w_gap.exp: enum_rep
...

With target_board unix, we have instead:
...
(gdb) PASS: gdb.ada/arr_acc_idx_w_gap.exp: print s(2)
print enum_with_gaps'enum_rep(lit3)^M
$16 = 13^M
(gdb) PASS: gdb.ada/arr_acc_idx_w_gap.exp: enum_rep
...

The error happens here:
...
8828      if (!types_equal (type, arg->type ()))
8829        error (_("'Enum_Rep requires argument to have same type as enum"));
...
because these types are not considered equal:
...
(gdb) p type->name ()
$1 = 0x7fffe4673e7d "enum_with_gap__enum_with_gaps"
(gdb) p arg->type()->name ()
$2 = 0x7fffe467411f "enum_with_gap__enum_subrangeB"
...

With target_board_unix, we have instead:
...
(gdb) p type->name ()
$1 = 0x7fffcc666c2d "enum_with_gap__enum_with_gaps"
(gdb) p arg->type()->name ()
$2 = 0x7fffcc666c2d "enum_with_gap__enum_with_gaps"
...

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

             reply	other threads:[~2023-08-06 13:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-06 13:06 vries at gcc dot gnu.org [this message]
2023-08-06 14:28 ` [Bug ada/30726] " vries at gcc dot gnu.org
2023-08-06 14:39 ` vries at gcc dot gnu.org
2023-08-06 15:05 ` tromey at sourceware dot org
2023-08-07  1:08 ` vries at gcc dot gnu.org
2023-09-06 13:04 ` vries at gcc dot gnu.org
2023-09-06 13:15 ` [Bug ada/30726] [gdb/ada] " vries at gcc dot gnu.org
2023-09-06 14:58 ` vries at gcc dot gnu.org
2023-09-06 15:27 ` vries at gcc dot gnu.org
2023-09-06 15:56 ` vries at gcc dot gnu.org
2023-09-06 18:02 ` vries at gcc dot gnu.org
2023-09-07 19:39 ` cvs-commit at gcc dot gnu.org
2023-09-07 19:41 ` vries at gcc dot gnu.org

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-30726-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).