Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 17/31] Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit
Date: Thu, 08 Jun 2023 14:17:45 +0100	[thread overview]
Message-ID: <87r0qmytxi.fsf@redhat.com> (raw)
In-Reply-To: <20221212203101.1034916-18-pedro@palves.net>

Pedro Alves <pedro@palves.net> writes:

> 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.

LGTM.

Reviewed-By: Andrew Burgess <aburgess@redhat.com>

Thanks,
Andrew

>
> Change-Id: I96b719fdf7fee94709e98bb3a90751d8134f3a38
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338
> ---
>  gdb/infrun.c        | 15 ++++++++++-----
>  gdb/remote.c        |  9 +++++++++
>  gdb/target/target.c |  1 +
>  gdb/target/target.h |  4 ++++
>  4 files changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/gdb/infrun.c b/gdb/infrun.c
> index 6fdffb31884..e47e3c688e7 100644
> --- a/gdb/infrun.c
> +++ b/gdb/infrun.c
> @@ -2445,24 +2445,29 @@ do_target_resume (ptid_t resume_ptid, bool step, enum gdb_signal sig)
>    else
>      target_pass_signals (signal_pass);
>  
> -  /* Request that the target report thread-{created,cloned} events in
> -     the following situations:
> +  /* Request that the target report thread-{created,cloned,exited}
> +     events in the following situations:
>  
>       - If we are performing an in-line step-over-breakpoint, then we
>         will remove a breakpoint from the target and only run the
>         current thread.  We don't want any new thread (spawned by the
> -       step) to start running, as it might miss the breakpoint.
> +       step) to start running, as it might miss the breakpoint.  We
> +       need to clear the step-over state if the stepped thread exits,
> +       so we also enable thread-exit events.
>  
>       - If we are stepping over a breakpoint out of line (displaced
>         stepping) then we won't remove a breakpoint from the target,
>         but, if the step spawns a new clone thread, then we will need
>         to fixup the $pc address in the clone child too, so we need it
> -       to start stopped.
> +       to start stopped.  We need to release the displaced stepping
> +       buffer if the stepped thread exits, so we also enable
> +       thread-exit events.
>    */
>    if (step_over_info_valid_p ()
>        || displaced_step_in_progress_thread (tp))
>      {
> -      gdb_thread_options options = GDB_THREAD_OPTION_CLONE;
> +      gdb_thread_options options
> +	= GDB_THREAD_OPTION_CLONE | GDB_THREAD_OPTION_EXIT;
>        if (target_supports_set_thread_options (options))
>  	tp->set_thread_options (options);
>        else
> diff --git a/gdb/remote.c b/gdb/remote.c
> index f7ab8523fd5..0d2b7c09a07 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -3998,6 +3998,15 @@ remote_target::update_thread_list ()
>  	      if (has_single_non_exited_thread (tp->inf))
>  		continue;
>  
> +	      /* Do not remove the thread if we've requested to be
> +		 notified of its exit.  For example, the thread may be
> +		 displaced stepping, infrun will need to handle the
> +		 exit event, and displaced stepping info is recorded
> +		 in the thread object.  If we deleted the thread now,
> +		 we'd lose that info.  */
> +	      if ((tp->thread_options () & GDB_THREAD_OPTION_EXIT) != 0)
> +		continue;
> +
>  	      /* Not found.  */
>  	      delete_thread (tp);
>  	    }
> diff --git a/gdb/target/target.c b/gdb/target/target.c
> index 453167a2ad4..2dc033e63b7 100644
> --- a/gdb/target/target.c
> +++ b/gdb/target/target.c
> @@ -196,6 +196,7 @@ to_string (gdb_thread_options options)
>  {
>    static constexpr gdb_thread_options::string_mapping mapping[] = {
>      MAP_ENUM_FLAG (GDB_THREAD_OPTION_CLONE),
> +    MAP_ENUM_FLAG (GDB_THREAD_OPTION_EXIT),
>    };
>    return options.to_string (mapping);
>  }
> diff --git a/gdb/target/target.h b/gdb/target/target.h
> index 139e371e8d8..4e8839c5667 100644
> --- a/gdb/target/target.h
> +++ b/gdb/target/target.h
> @@ -34,6 +34,10 @@ enum gdb_thread_option : unsigned
>    /* Tell the target to report TARGET_WAITKIND_THREAD_CLONED events
>       for the thread.  */
>    GDB_THREAD_OPTION_CLONE = 1 << 0,
> +
> +  /* Tell the target to report TARGET_WAITKIND_THREAD_EXIT events for
> +     the thread.  */
> +  GDB_THREAD_OPTION_EXIT = 1 << 1,
>  };
>  
>  DEF_ENUM_FLAGS_TYPE (enum gdb_thread_option, gdb_thread_options);
> -- 
> 2.36.0


  reply	other threads:[~2023-06-08 13:18 UTC|newest]

Thread overview: 100+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 20:30 [PATCH 00/31] Step over thread clone and thread exit Pedro Alves
2022-12-12 20:30 ` [PATCH 01/31] displaced step: pass down target_waitstatus instead of gdb_signal Pedro Alves
2023-02-03 10:44   ` Andrew Burgess via Gdb-patches
2023-03-10 17:15     ` Pedro Alves
2023-03-16 16:07       ` Andrew Burgess via Gdb-patches
2023-03-22 21:29         ` Andrew Burgess via Gdb-patches
2023-03-23 15:15           ` Pedro Alves
2023-03-27 12:40             ` Andrew Burgess via Gdb-patches
2023-03-27 16:21               ` Pedro Alves
2022-12-12 20:30 ` [PATCH 02/31] linux-nat: introduce pending_status_str Pedro Alves
2023-02-03 12:00   ` Andrew Burgess via Gdb-patches
2023-03-10 17:15     ` Pedro Alves
2023-03-16 16:19       ` Andrew Burgess via Gdb-patches
2023-03-27 18:05         ` Pedro Alves
2022-12-12 20:30 ` [PATCH 03/31] gdb/linux: Delete all other LWPs immediately on ptrace exec event Pedro Alves
2023-03-21 14:50   ` Andrew Burgess via Gdb-patches
2023-04-04 13:57     ` Pedro Alves
2023-04-14 19:29       ` Pedro Alves
2023-05-26 15:04         ` Andrew Burgess via Gdb-patches
2023-11-13 14:04           ` Pedro Alves
2023-05-26 14:45       ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 04/31] Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THREAD_CLONED Pedro Alves
2023-02-04 15:38   ` Andrew Burgess via Gdb-patches
2023-03-10 17:16     ` Pedro Alves
2023-03-21 16:06       ` Andrew Burgess via Gdb-patches
2023-11-13 14:05         ` Pedro Alves
2022-12-12 20:30 ` [PATCH 05/31] Support clone events in the remote protocol Pedro Alves
2023-03-22 15:46   ` Andrew Burgess via Gdb-patches
2023-11-13 14:05     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 06/31] Avoid duplicate QThreadEvents packets Pedro Alves
2023-05-26 15:53   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 07/31] enum_flags to_string Pedro Alves
2023-01-30 20:07   ` Simon Marchi via Gdb-patches
2022-12-12 20:30 ` [PATCH 08/31] Thread options & clone events (core + remote) Pedro Alves
2023-01-31 12:25   ` Lancelot SIX via Gdb-patches
2023-03-10 19:16     ` Pedro Alves
2023-06-06 13:29       ` Andrew Burgess via Gdb-patches
2023-11-13 14:07         ` Pedro Alves
2022-12-12 20:30 ` [PATCH 09/31] Thread options & clone events (native Linux) Pedro Alves
2023-06-06 13:43   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 10/31] Thread options & clone events (Linux GDBserver) Pedro Alves
2023-06-06 14:12   ` Andrew Burgess via Gdb-patches
2023-11-13 14:07     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 11/31] gdbserver: Hide and don't detach pending clone children Pedro Alves
2023-06-07 16:10   ` Andrew Burgess via Gdb-patches
2023-11-13 14:08     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 12/31] Remove gdb/19675 kfails (displaced stepping + clone) Pedro Alves
2023-06-07 17:08   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 13/31] Add test for stepping over clone syscall Pedro Alves
2023-06-07 17:42   ` Andrew Burgess via Gdb-patches
2023-11-13 14:09     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 14/31] all-stop/synchronous RSP support thread-exit events Pedro Alves
2023-06-07 17:52   ` Andrew Burgess via Gdb-patches
2023-11-13 14:11     ` Pedro Alves
2023-12-15 18:15       ` Pedro Alves
2022-12-12 20:30 ` [PATCH 15/31] gdbserver/linux-low.cc: Ignore event_ptid if TARGET_WAITKIND_IGNORE Pedro Alves
2022-12-12 20:30 ` [PATCH 16/31] Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core Pedro Alves
2023-06-08 12:27   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 17/31] Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit Pedro Alves
2023-06-08 13:17   ` Andrew Burgess via Gdb-patches [this message]
2022-12-12 20:30 ` [PATCH 18/31] Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver Pedro Alves
2023-06-08 14:14   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 19/31] Implement GDB_THREAD_OPTION_EXIT support for native Linux Pedro Alves
2023-06-08 14:17   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 20/31] gdb: clear step over information on thread exit (PR gdb/27338) Pedro Alves
2023-06-08 15:29   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 21/31] stop_all_threads: (re-)enable async before waiting for stops Pedro Alves
2023-06-08 15:49   ` Andrew Burgess via Gdb-patches
2023-11-13 14:12     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 22/31] gdbserver: Queue no-resumed event after thread exit Pedro Alves
2023-06-08 18:16   ` Andrew Burgess via Gdb-patches
2023-11-13 14:12     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 23/31] Don't resume new threads if scheduler-locking is in effect Pedro Alves
2023-06-08 18:24   ` Andrew Burgess via Gdb-patches
2023-11-13 14:12     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 24/31] Report thread exit event for leader if reporting thread exit events Pedro Alves
2023-06-09 13:11   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 25/31] Ignore failure to read PC when resuming Pedro Alves
2023-06-10 10:33   ` Andrew Burgess via Gdb-patches
2023-11-13 14:13     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 26/31] gdb/testsuite/lib/my-syscalls.S: Refactor new SYSCALL macro Pedro Alves
2023-06-10 10:33   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 27/31] Testcases for stepping over thread exit syscall (PR gdb/27338) Pedro Alves
2023-06-12  9:53   ` Andrew Burgess via Gdb-patches
2022-12-12 20:30 ` [PATCH 28/31] Document remote clone events, and QThreadOptions packet Pedro Alves
2023-06-05 15:53   ` Andrew Burgess via Gdb-patches
2023-11-13 14:13     ` Pedro Alves
2023-06-12 12:06   ` Andrew Burgess via Gdb-patches
2023-11-13 14:15     ` Pedro Alves
2022-12-12 20:30 ` [PATCH 29/31] inferior::clear_thread_list always silent Pedro Alves
2023-06-12 12:20   ` Andrew Burgess via Gdb-patches
2022-12-12 20:31 ` [PATCH 30/31] Centralize "[Thread ...exited]" notifications Pedro Alves
2023-02-04 16:05   ` Andrew Burgess via Gdb-patches
2023-03-10 17:21     ` Pedro Alves
2023-02-16 15:40   ` Andrew Burgess via Gdb-patches
2023-06-12 12:23     ` Andrew Burgess via Gdb-patches
2022-12-12 20:31 ` [PATCH 31/31] Cancel execution command on thread exit, when stepping, nexting, etc Pedro Alves
2023-06-12 13:12   ` Andrew Burgess via Gdb-patches
2023-01-24 19:47 ` [PATCH v3 00/31] Step over thread clone and thread exit Pedro Alves
2023-11-13 14:24 ` [PATCH " Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0qmytxi.fsf@redhat.com \
    --to=gdb-patches@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=pedro@palves.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox