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 B9682382E82C; Mon,  7 Jun 2021 13:29:41 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B9682382E82C
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/27908] FAIL: gdb.base/run-attach-while-running.exp:
 threaded=1: run-or-attach=attach: non-stop=on: test: attach to process
 (timeout)
Date: Mon, 07 Jun 2021 13:29:41 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-27908-4717-ladt2Bx2tc@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27908-4717@http.sourceware.org/bugzilla/>
References: <bug-27908-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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2021 13:29:41 -0000

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|gdb                         |testsuite

--- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #9)
> (In reply to Tom de Vries from comment #8)
> > Looks like a regression, passed at gdb-10-branch branchpoint.
>=20
> Hmm, that bisects to:
> ...
> commit 2ab76a181f3db93f051aaae66d65ff2733884d96
> Author: Pedro Alves <pedro@palves.net>
> Date:   Wed Dec 23 00:34:54 2020 +0000
>=20
>     Fix attaching in non-stop mode (PR gdb/27055)
> ...
>=20
> Looking in the test-case attach-non-stop.exp, it seems that the "thread
> stopped" message is expected.
>=20
> This makes no sense to me.   In non-stop mode, I'm expecting only one thr=
ead
> to stop.  Why do we expect all threads to stop?  Isn't that all-stop mode
> behaviour?

After rereading the documentation once more, I guess not.  The non-stop mode
only affects moments when "a thread stops to report a debugging event".  So=
, I
guess attaching is not a debugging event? I was not able to find a definiti=
on.

Anyway, I've submitted an RFC patch (
https://sourceware.org/pipermail/gdb-patches/2021-June/179615.html ) that
documents the behaviour of attach in non-stop mode, hopefully that will make
things a bit easier to understand.

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