[Bug gdb/27338] Stepping over a breakpoint on an instruction that makes the thread exit is not correctly handled

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

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

--- Comment #5 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=d8d96409c83f84f5c15d2e846a7c0a59ceed187c

commit d8d96409c83f84f5c15d2e846a7c0a59ceed187c
Author: Pedro Alves <pedro@palves.net>
Date:   Thu Mar 17 19:25:03 2022 +0000

    Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit

    When stepping over a breakpoint with displaced stepping, GDB needs to
    be informed if the stepped thread exits, otherwise the displaced
    stepping buffer that was allocated to that thread leaks, and this can
    result in deadlock, with other threads waiting for their turn to
    displaced step, but their turn never comes.

    Similarly, when stepping over a breakpoint in line, GDB also needs to
    be informed if the stepped thread exits, so that is can clear the step
    over state and re-resume threads.

    This commit makes it possible for GDB to ask the target to report
    thread exit events for a given thread, using the new "thread options"
    mechanism introduced by a previous patch.

    This only adds the core bits.  Following patches in the series will
    teach the Linux backends (native & gdbserver) to handle the
    GDB_THREAD_OPTION_EXIT option, and then a later patch will make use of
    these thread exit events to clean up displaced stepping and inline
    stepping state properly.

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

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