Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, revision 8a522c6cab56bd55f1454638786f999f6f636354
Date: Fri, 03 May 2019 07:20:00 -0000	[thread overview]
Message-ID: <1556868031.1511.8.camel@skynet.be> (raw)
In-Reply-To: <E1hM4JI-0006OW-In@kwanyin.sergiodj.net>

On Thu, 2019-05-02 at 01:31 -0400, gdb-buildbot@sergiodj.net wrote:
> Unfortunately it seems that there is a breakage on GDB.
> 
> Commit title: 'Have 'thread|frame apply' style their output.'
> Revision: 8a522c6cab56bd55f1454638786f999f6f636354
Note that this is the build failure when guile is enabled.
It was fixed the 28 of April in fa731fa0d400568

Philippe


  reply	other threads:[~2019-05-03  7:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-02  5:31 Oh dear. I regret to inform you that commit 8a522c6cab56bd55f1454638786f999f6f636354 might be unfortunate gdb-buildbot
2019-05-02  5:31 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m32, revision 8a522c6cab56bd55f1454638786f999f6f636354 gdb-buildbot
2019-05-03  7:20   ` Philippe Waroquiers [this message]
2019-05-02  5:35 ` Breakage on builder Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-05-02  5:39 ` Breakage on builder Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2019-05-02  5:46 ` Breakage on builder Fedora-x86_64-m64, " gdb-buildbot
2019-05-02  5:52 ` Breakage on builder Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-05-04  8:55 ` Breakage on builder Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-05-05  5:39 ` Breakage on builder Fedora-x86_64-m32, " gdb-buildbot

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=1556868031.1511.8.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb-buildbot@sergiodj.net \
    --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