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 0E87C3857011; Fri, 10 Jul 2020 22:57:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0E87C3857011
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:41 +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-6tpA4aKQkP@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:42 -0000

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

--- 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 Pedro Alves <palves@sourceware.org>:

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

commit 42bd97a6b1e5fa845af116ce52af1a8a3a58be7c
Author: Pedro Alves <pedro@palves.net>
Date:   Sat Jul 4 19:31:21 2020 +0100

    Avoid constant stream of TARGET_WAITKIND_NO_RESUMED

    If we hit the synchronous execution command case described by
    handle_no_resumed, and handle_no_resumed determines that the event
    should be ignored, because it found a thread that is executing, we end
    up in prepare_to_wait.

    There, if the current target is not registered in the event loop right
    now, we call mark_infrun_async_event_handler.  With that event handler
    marked, the event loop calls again into fetch_inferior_event, which
    calls target_wait, which returns TARGET_WAITKIND_NO_RESUMED, and we
    end up in handle_no_resumed, again ignoring the event and marking
    infrun_async_event_handler.  The result is that GDB is now always
    keeping the CPU 100% busy in this loop, even though it continues to be
    able to react to input and to real target events, because we still go
    through the event-loop.

    The problem is that marking of the infrun_async_event_handler in
    prepare_to_wait.  That is there to handle targets that don't support
    asynchronous execution.  So the correct predicate is whether async
    execution is supported, not whether the target is async right now.

    gdb/ChangeLog:

            PR gdb/26199
            * infrun.c (prepare_to_wait): Check target_can_async_p instead =
of
            target_is_async_p.

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