Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gcc-patches@gcc.gnu.org,  gdb-patches@sourceware.org
Subject: Re: [PATCH] contrib: Make dg-extract-results.py tolerant of unparseable files
Date: Thu, 28 May 2026 13:01:11 -0600	[thread overview]
Message-ID: <87h5nr5pfs.fsf@tromey.com> (raw)
In-Reply-To: <20260514181502.2841511-2-kevinb@redhat.com> (Kevin Buettner's message of "Thu, 14 May 2026 11:15:03 -0700")

>>>>> "Kevin" == Kevin Buettner <kevinb@redhat.com> writes:

Kevin> This commit fixes this GDB bug:
Kevin> https://sourceware.org/bugzilla/show_bug.cgi?id=34147

FWIW I think this should go in.

It would be fine to land it in gdb and then merge it back.
I think we agreed that common files could be treated this way now.

Kevin> +class ParseError (Exception):

I guess gcc doesn't use 'black' for Python formatting.

thanks,
Tom

  reply	other threads:[~2026-05-28 19:01 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 [this message]
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

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=87h5nr5pfs.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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