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 6AF923858430; Tue, 10 Oct 2023 16:42:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6AF923858430
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1696956157;
	bh=MRncZM5t0UjSG2iuWswQ61KIqJ08kVWGJZqmZKiV+14=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=w02mt/0NSs7mZE5z/J6MFYM53GZImDaqbFXzGvPUu6Vfh2AqNO9tbEZUxGE7W+6Pd
	 AHIyLW8BRB5+m+PhMgv2ysTWEVzy1+DJcFn7f2IxLqOaTg7EL5uAzbhm44Ucrdm3i5
	 ISFHbsYTO2vVAlHv4WoFUnOvHW1x4qrd1bzgFucQ=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30630] remote.c:8352: internal-error: wait: Assertion
 `!async_event_handler_marked (rs->remote_async_inferior_event_token)' failed.
Date: Tue, 10 Oct 2023 16:42:36 +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: unknown
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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-30630-4717-B1vKzp4r61@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30630-4717@http.sourceware.org/bugzilla/>
References: <bug-30630-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=3D30630

--- Comment #10 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot g=
nu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:

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

commit 635b2dd919b8c58e164b77c396041935fca1d66a
Author: Simon Marchi <simon.marchi@efficios.com>
Date:   Tue Oct 3 22:04:01 2023 -0400

    gdb: add assertion when marking the remote async flag

    As reported in bug 30630 [1], we hit a case where the remote target's
    async flag is marked while the target is not configured (yet) to work
    async.  This should not happen.  It is caught thanks to this assert in
    remote_target::wait:

        /* Start by clearing the flag that asks for our wait method to be
called,
           we'll mark it again at the end if needed.  If the target is not =
in
           async mode then the async token should not be marked.  */
        if (target_is_async_p ())
          rs->clear_async_event_handler ();
        else
          gdb_assert (!rs->async_event_handler_marked ());

    This is helpful, but I think that we could have caught the problem earl=
ier
than
    that, at the moment we marked the handler.  Catching problems earlier
    makes them easier to debug.

    [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3D30630

    Change-Id: I7e229c74b04da82bef6a817d5a676be5cf52e833
    Approved-By: Andrew Burgess <aburgess@redhat.com>

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