From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.python/py-selected-context.exp regexp
Date: Wed, 19 Aug 2026 10:36:56 +0200 [thread overview]
Message-ID: <600ceca1-8fe2-4fdf-a356-3282f317ce65@suse.de> (raw)
In-Reply-To: <20260803080721.859964-1-tdevries@suse.de>
On 8/3/26 10:07 AM, Tom de Vries wrote:
> Still, the test should not fail. This may be an expect bug, or a
> miscompilation of expect. I've filed a testsuite PR [1] about it for further
> investigation.
I've pushed this, with an update to this text to reflect that indeed
there was an expect bug:
...
Still, the test should not fail. It fails due to an expect bug [1][2].
...
Thanks,
- Tom
prev parent reply other threads:[~2026-08-19 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 8:07 Tom de Vries
2026-08-19 8:36 ` Tom de Vries [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=600ceca1-8fe2-4fdf-a356-3282f317ce65@suse.de \
--to=tdevries@suse.de \
--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