[Bug gdb/27830] Attempt to resume already running thread

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

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

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=53de5394f7bf11995b1d9cb6885a8490b2ebc9da

commit 53de5394f7bf11995b1d9cb6885a8490b2ebc9da
Author: Pedro Alves <pedro@palves.net>
Date:   Tue Nov 23 20:35:12 2021 +0000

    Support clone events in the remote protocol

    The previous patch taught GDB about a new
    TARGET_WAITKIND_THREAD_CLONED event kind, and made the Linux target
    report clone events.

    A following patch will teach Linux GDBserver to do the same thing.

    But before we get there, we need to teach the remote protocol about
    TARGET_WAITKIND_THREAD_CLONED.  That's what this patch does.  Clone is
    very similar to vfork and fork, and the new stop reply is likewise
    handled similarly.  The stub reports "T05clone:...".

    GDBserver core is taught to handle TARGET_WAITKIND_THREAD_CLONED and
    forward it to GDB in this patch, but no backend actually emits it yet.
    That will be done in a following patch.

    Documentation for this new remote protocol feature is included in a
    documentation patch later in the series.

    Reviewed-By: Andrew Burgess <aburgess@redhat.com>
    Change-Id: If271f20320d864f074d8ac0d531cc1a323da847f
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=19675
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27830

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