public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/31238] FAIL: gdb.python/py-inferior.exp: test repr of an invalid thread
Date: Fri, 12 Jan 2024 18:05:47 +0000 [thread overview]
Message-ID: <bug-31238-4717-OBEFCqaDGd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31238-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31238
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |15.1
Status|NEW |RESOLVED
Resolution|--- |FIXED
Component|gdb |testsuite
--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Andrew Burgess from comment #4)
> Tom,
>
> I'll leave you to close this bug once you've confirmed the fix is working.
> The test was always passing for me, but I think the fix I pushed should
> resolve the problem.
It passes for me now on both systems, thanks for fixing this.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-12 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 14:35 [Bug gdb/31238] New: " vries at gcc dot gnu.org
2024-01-12 14:35 ` [Bug gdb/31238] " vries at gcc dot gnu.org
2024-01-12 14:36 ` vries at gcc dot gnu.org
2024-01-12 14:53 ` vries at gcc dot gnu.org
2024-01-12 16:19 ` cvs-commit at gcc dot gnu.org
2024-01-12 16:21 ` aburgess at redhat dot com
2024-01-12 18:05 ` vries at gcc dot gnu.org [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=bug-31238-4717-OBEFCqaDGd@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).