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/29057] New: FAIL: gdb.ada/dynamic-iface.exp: print local as interface
Date: Wed, 13 Apr 2022 05:59:16 +0000	[thread overview]
Message-ID: <bug-29057-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29057
           Summary: FAIL: gdb.ada/dynamic-iface.exp: print local as
                    interface
           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: ---

On openSUSE Leap 15.3 I run into:
...
FAIL: gdb.ada/dynamic-iface.exp: print local as interface
FAIL: gdb.ada/dynamic-iface.exp: print local2 as interface
...

First in more detail:
...
(gdb) print obj^M
$1 = ()^M
(gdb) FAIL: gdb.ada/dynamic-iface.exp: print local as interface
...

This is using gcc 7.5.0.

Fails up until gcc 11, starts passing at gcc 12.

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

             reply	other threads:[~2022-04-13  5:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  5:59 vries at gcc dot gnu.org [this message]
2022-04-13  6:00 ` [Bug ada/29057] " vries at gcc dot gnu.org
2022-05-13  5:55 ` vries at gcc dot gnu.org
2022-05-13  6:08 ` vries at gcc dot gnu.org
2022-05-13  7:31 ` vries at gcc dot gnu.org
2022-05-13  8:36 ` vries at gcc dot gnu.org
2022-05-23 13:47 ` [Bug ada/29057] [gcc-5 - gcc-8] " 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-29057-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).