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 25AD3383E816; Fri, 10 Jul 2020 22:57:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 25AD3383E816
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26199] GDB goes in busy loop when interrupting non-stop
 program
Date: Fri, 10 Jul 2020 22:57:47 +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: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 10.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26199-4717-sp52b77sUA@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26199-4717@http.sourceware.org/bugzilla/>
References: <bug-26199-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: <http://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: <http://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2020 22:57:47 -0000

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

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D7d3badc6a88b=
510f96c9aa0bab8f3375292d23bf

commit 7d3badc6a88b510f96c9aa0bab8f3375292d23bf
Author: Pedro Alves <pedro@palves.net>
Date:   Sat Jul 4 19:26:59 2020 +0100

    Fix handle_no_resumed w/ multiple targets

    handle_no_resumed is currently not considering multiple targets.

    Say you have two inferiors 1 and 2, each connected to a different
    target, A and B.

    Now say you set inferior 2 running, with "continue &".

    Now you select a thread of inferior 1, say thread 1.2, and continue in
    the foreground.  All other threads of inferior 1 are left stopped.
    Thread 1.2 exits, and thus target A has no other resumed thread, so it
    reports TARGET_WAITKIND_NO_RESUMED.

    At this point, if both inferiors were running in the same target,
    handle_no_resumed would realize that threads of inferior 2 are still
    executing, so the TARGET_WAITKIND_NO_RESUMED event should be ignored.
    But because handle_no_resumed only walks the threads of the current
    target, it misses noticing that threads of inferior 2 are still
    executing.  The fix is just to walk over all threads of all targets.

    A testcase covering the use case above will be added in a following
    patch.  It can't be added yet because it depends on yet another fix to
    handle_no_resumed not included here.

    gdb/ChangeLog:

            PR gdb/26199
            * infrun.c (handle_no_resumed): Handle multiple targets.

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