From: Nick Alcock <nick.alcock@oracle.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Breakage on builder Fedora-i686, revision 22ccb8495447fa2ea31b1f1dea7e94eecf97475d
Date: Mon, 14 Oct 2019 09:49:00 -0000 [thread overview]
Message-ID: <87zhi3ejwh.fsf@esperi.org.uk> (raw)
In-Reply-To: <E1iJ0gs-0005hm-2P@gdb-buildbot.osci.io> (gdb-buildbot@sergiodj.net's message of "Fri, 11 Oct 2019 15:35:06 -0400")
On 11 Oct 2019, gdb-buildbot@sergiodj.net stated:
> Unfortunately it seems that there is a breakage on GDB.
Oops, sorry!
This was just the result of a mis-squashing (the fix in bfd-elf.h that
switches the _bfd_elf_strtab_str offset to taking a bfd_size_type was
mistakenly dropped in the next commit rather than in this one, leading
to a brief period when 32-bit builds were broken) and will not affect
future development.
(I validate all intermediate commits in series like this for
compilability, but not on all possible platforms. Maybe I should add
32-bit compilability tests to that set.)
prev parent reply other threads:[~2019-10-14 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 19:35 Oh dear. I regret to inform you that commit 22ccb8495447fa2ea31b1f1dea7e94eecf97475d might be unfortunate gdb-buildbot
2019-10-11 19:35 ` Breakage on builder Fedora-i686, revision 22ccb8495447fa2ea31b1f1dea7e94eecf97475d gdb-buildbot
2019-10-14 9:49 ` Nick Alcock [this message]
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=87zhi3ejwh.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=gdb-patches@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