From: Stephen Roberts <Stephen.Roberts@arm.com>
To: "gdb-buildbot@sergiodj.net" <gdb-buildbot@sergiodj.net>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: Oh dear. I regret to inform you that commit 4ee89e903de920496a69c01df70db13a70a2a0be might be unfortunate
Date: Tue, 20 Mar 2018 14:29:00 -0000 [thread overview]
Message-ID: <AM3PR08MB0625E48DC69491173523E2A0FBAB0@AM3PR08MB0625.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <4ee89e903de920496a69c01df70db13a70a2a0be-master-breakage@gdb-build>
Apologies, I'm looking into this as a matter of urgency. It appears that my patch has caused the indentation of the following block to become incorrect.
Sorry,
Stephen R.
---------
From: gdb-buildbot@sergiodj.net <gdb-buildbot@sergiodj.net>
Sent: 20 March 2018 14:14
To: Stephen Roberts; gdb-patches@sourceware.org
Subject: Oh dear. I regret to inform you that commit 4ee89e903de920496a69c01df70db13a70a2a0be might be unfortunate
My lords, ladies, gentlemen, members of the public.
It is a matter of great regret and sadness to inform you that commit:
Replace the linear search in find_pc_sect_line with a binary search.
4ee89e903de920496a69c01df70db13a70a2a0be
might have made GDB unwell. Since I am just your Butler BuildBot,
I kindly ask that a human superior officer double-check this.
Please note that if you are reading this message on gdb-patches, there might
be other builders broken.
You can find more details about the unfortunate breakage in the next messages.
Cheers,
Your GDB BuildBot.
prev parent reply other threads:[~2018-03-20 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 14:14 gdb-buildbot
2018-03-20 14:14 ` Breakage on builder Fedora-i686, revision 4ee89e903de920496a69c01df70db13a70a2a0be gdb-buildbot
2018-03-20 14:16 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2018-03-20 14:16 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2018-03-20 14:17 ` Breakage on builder Fedora-s390x-m64, " gdb-buildbot
2018-03-20 14:17 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot
2018-03-20 14:21 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2018-03-20 14:23 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2018-03-20 14:24 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2018-03-20 14:24 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2018-03-20 14:29 ` Stephen Roberts [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=AM3PR08MB0625E48DC69491173523E2A0FBAB0@AM3PR08MB0625.eurprd08.prod.outlook.com \
--to=stephen.roberts@arm.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
/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).