public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Binutils Development <binutils@sourceware.org>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	Nick Clifton <nickc@redhat.com>
Subject: [buildbot] GDB regression on 85880250e591a51624d24db653aaace0c5ce5943
Date: Tue, 06 Jan 2015 21:11:00 -0000	[thread overview]
Message-ID: <87h9w34nso.fsf@sergiodj.net> (raw)

Hi,

Nick's commit:

  <https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commitdiff;h=85880250e591a51624d24db653aaace0c5ce5943;hp=fce10a8494efa8faec67b718f25e06d3d71694b3>

Introduced some regressions on GDB (they were caught by the BuildBot I
have running here, yay!).  I did not investigate them further yet, but I
thought it would be better to mention them here.  If nobody fixes this
soon, I intend to look at them tonight.

The regressions are all of the form:

  restore
  /home/buildbot/fedora-x86-64-2/fedora-x86-64/build/gdb/testsuite/gdb.base/intstr1.tekhex
  '/home/buildbot/fedora-x86-64-2/fedora-x86-64/build/gdb/testsuite/gdb.base/intstr1.tekhex' is not a recognized file format.
  (gdb) FAIL: gdb.base/dump.exp: struct as value, tekhex; file restored ok

On a side note, I can't find Nick's message mentioning the patch on the
binutils ml.

Cheers,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

             reply	other threads:[~2015-01-06 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 21:11 Sergio Durigan Junior [this message]
2015-01-09 21:59 ` Nicholas Clifton
2015-01-09 22:24   ` Sergio Durigan Junior

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=87h9w34nso.fsf@sergiodj.net \
    --to=sergiodj@sergiodj.net \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.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).