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 gdb/29227] [gdb, m32] FAIL: gdb.base/corefile.exp: core-file warning-free
Date: Mon, 06 Jun 2022 18:14:58 +0000 [thread overview]
Message-ID: <bug-29227-4717-gPdl7KVlgp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29227-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29227
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Reproduces with gdb-12-branch and gdb-11-branch.
So why didn't I see this before?
Because this is with "--enable-targets=all", and I used to build with the
opensuse gdb package equivalent
"--enable-targets=i686-suse-linux,powerpc-suse-linux,powerpc64-suse-linux,powerpc64le-suse-linux,s390-suse-linux,s390x-suse-linux,x86_64-suse-linux,arm-suse-linux,aarch64-suse-linux,m68k-suse-linux,riscv64-suse-linux,ia64-suse-linux,spu-elf
--enable-obsolete".
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-06 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:02 [Bug gdb/29227] New: " vries at gcc dot gnu.org
2022-06-06 6:06 ` [Bug gdb/29227] " vries at gcc dot gnu.org
2022-06-06 7:03 ` vries at gcc dot gnu.org
2022-06-06 18:14 ` vries at gcc dot gnu.org [this message]
2022-06-07 6:38 ` vries at gcc dot gnu.org
2022-06-08 7:37 ` vries at gcc dot gnu.org
2022-06-09 8:59 ` vries at gcc dot gnu.org
2024-01-05 15:36 ` ssbssa at sourceware dot org
2024-01-05 15:43 ` 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-29227-4717-gPdl7KVlgp@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).