[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 #9 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=393a6b5947d037a55ce1b57474e1ffb3074f544e

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

    Thread options & clone events (Linux GDBserver)

    This patch teaches the Linux GDBserver backend to report clone events
    to GDB, when GDB has requested them with the GDB_THREAD_OPTION_CLONE
    thread option, via the new QThreadOptions packet.

    This shuffles code in linux_process_target::handle_extended_wait
    around to a more logical order when we now have to handle and
    potentially report all of fork/vfork/clone.

    Raname lwp_info::fork_relative -> lwp_info::relative as the field is
    no longer only about (v)fork.

    With this, gdb.threads/stepi-over-clone.exp now cleanly passes against
    GDBserver, so remove the native-target-only requirement from that
    testcase.

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

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