From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 744813858005; Thu, 10 Aug 2023 17:47:02 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 744813858005
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1691689622;
	bh=X98n2iF6iairoNgQdT/+Dqw6Cq6uiNy2YL9CHuMrbYw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XBeulpxhDjSnH+vyKP3lGkACJ2kf1xCwNXvQ6x2gkSQUXCcNrGsL7EueAi+EdMiqX
	 6PzGDdR1Zwxs6Ss+847jBkBxZd/A/X2ZWZz6YNK4T7FcOIWLa5AWc7GsUeOnCwEcd+
	 5FuurLnK0OC2nhV+lQOdqqhYxl5QLs7vEk59jH90=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30677] [native-gdbserver] FAIL:
 gdb.python/py-thread-exited.exp: python print(threadOneExit)
Date: Thu, 10 Aug 2023 17:47:01 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: tromey at sourceware dot org
X-Bugzilla-Target-Milestone: 14.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30677-4717-d0kXbWM0U0@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30677-4717@http.sourceware.org/bugzilla/>
References: <bug-30677-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D30677

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D78e7f66e75f9=
3d49a7accf3a7552b2378533b52b

commit 78e7f66e75f93d49a7accf3a7552b2378533b52b
Author: Tom Tromey <tromey@adacore.com>
Date:   Mon Jul 31 11:30:30 2023 -0600

    Change py-thread-exited.exp to work with gdbserver

    gdbserver does not notify gdb of new threads when they are created.
    I'm not sure if this is documented anywhere, but it is mentioned on
    this page:

    https://sourceware.org/gdb/wiki/LocalRemoteFeatureParity

    Search for "Finding new threads in the inferior".

    This behavior is a bit unfortunate -- I would think that it would be
    better to arrange for such notification if something on the gdb side
    is interested.

    Meanwhile, this patch fixes py-thread-exited.exp to work around this
    problem.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30677

--=20
You are receiving this mail because:
You are on the CC list for the bug.=