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 tdep/29419] [gdb, tdep/aarch64,ppc64le,s390x] FAIL: gdb.ada/inline-section-gc.exp: break callee.adb:22
Date: Wed, 27 Jul 2022 15:01:08 +0000	[thread overview]
Message-ID: <bug-29419-4717-xtQvcBqjCt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29419-4717@http.sourceware.org/bugzilla/>

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[gdb, tdep/aarch64] FAIL:   |[gdb,
                   |gdb.ada/inline-section-gc.e |tdep/aarch64,ppc64le,s390x]
                   |xp: break callee.adb:22     |FAIL:
                   |                            |gdb.ada/inline-section-gc.e
                   |                            |xp: break callee.adb:22

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Observed the same fail with powerpc and s390x.

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

  parent reply	other threads:[~2022-07-27 15:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 14:44 [Bug tdep/29419] New: [gdb, tdep/aarch64] " vries at gcc dot gnu.org
2022-07-27 14:44 ` [Bug tdep/29419] " vries at gcc dot gnu.org
2022-07-27 14:49 ` luis.machado at arm dot com
2022-07-27 14:50 ` luis.machado at arm dot com
2022-07-27 15:01 ` vries at gcc dot gnu.org [this message]
2022-07-27 15:04 ` [Bug tdep/29419] [gdb, tdep/aarch64,ppc64le,s390x] " vries at gcc dot gnu.org
2022-07-27 15:37 ` vries at gcc dot gnu.org
2022-07-27 16:17 ` vries at gcc dot gnu.org
2022-08-10 13:49 ` 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-29419-4717-xtQvcBqjCt@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).