Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.python/py-mi-cmd.exp
Date: Wed, 12 Aug 2026 14:16:38 -0600	[thread overview]
Message-ID: <875x1fw0ux.fsf@tromey.com> (raw)
In-Reply-To: <20260804153150.1389153-1-tdevries@suse.de> (Tom de Vries's message of "Tue, 4 Aug 2026 17:31:50 +0200")

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> On Fedora Rawhide aarch64-linux (using Python 3.15.0b4), with test-case
Tom> gdb.python/py-mi-cmd.exp I ran into:
Tom> ...
Tom> Expecting: ^(-pycmd bk3[^M
Tom> ]+)?(&"TypeError.*: __repr__ returned non-string \(type BadKey\).."^M
Tom> \^error,msg="Error occurred in Python: __repr__ returned non-string \(type BadKey\)"[^M
Tom> ]+[(]gdb[)] ^M
Tom> [ ]*)
Tom> -pycmd bk3^M
Tom> &"TypeError: ReallyBadKey.__repr__() must return a str, not BadKey\n"^M
Tom> ^error,msg="Error occurred in Python: ReallyBadKey.__repr__() must return a str, not BadKey"^M
Tom> (gdb) ^M
Tom> FAIL: $exp: -pycmd bk3 (unexpected output)
Tom> ...

Tom> Fix this by updating the regexp.

Looks fine to me, thanks.
Approved-By: Tom Tromey <tom@tromey.com>

Tom

      reply	other threads:[~2026-08-12 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 15:31 Tom de Vries
2026-08-12 20:16 ` Tom Tromey [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=875x1fw0ux.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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