Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] contrib: Make dg-extract-results.py tolerant of unparseable files
Date: Fri, 29 May 2026 17:48:53 -0700	[thread overview]
Message-ID: <20260529174853.17305ff3@f42-zbm-amd> (raw)
In-Reply-To: <20260529130403.249b662b@f42-zbm-amd>

On Fri, 29 May 2026 13:04:03 -0700
Kevin Buettner <kevinb@redhat.com> wrote:

> For copying back to GDB (binutils-gdb), I plan to wait until the
> ChangeLog entry is in place.  Once that is done, I'll do the copy and
> push to GDB as well.

I found that binutils-gdb has a minimal contrib/ChangeLog file noting
when files have been copied from GCC.  I added an entry of my own
along with copying over dg-extract-results.py.  The commit log
describing the change and why it is needed is the same as what went
into gcc though.

In any case, it's pushed.  That means that we'll no longer see empty
gdb.sum and gdb.log files when testing Fedora 44 and Rawhide.

In addition, I pushed another fix earlier today which fixes the
UTF-8 issues which were causing the zero-sized files:

[gdb/testsuite, Tcl 9] Fix EILSEQ problems for UTF8 related tests

Kevin


      reply	other threads:[~2026-05-30  0:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-14 18:15 Kevin Buettner
2026-05-28 19:01 ` Tom Tromey
2026-05-28 19:21   ` Andrew Pinski
2026-05-28 23:38     ` Andrew Pinski
2026-05-29  0:53       ` Simon Marchi
2026-05-28 23:35 ` Andrew Pinski
2026-05-29 20:04   ` Kevin Buettner
2026-05-30  0:48     ` Kevin Buettner [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=20260529174853.17305ff3@f42-zbm-amd \
    --to=kevinb@redhat.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