public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 05/31] Support clone events in the remote protocol
Date: Wed, 22 Mar 2023 15:46:01 +0000	[thread overview]
Message-ID: <87cz50dc1y.fsf@redhat.com> (raw)
In-Reply-To: <20221212203101.1034916-6-pedro@palves.net>

Pedro Alves <pedro@palves.net> writes:

> 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.
>
> Change-Id: If271f20320d864f074d8ac0d531cc1a323da847f
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=19675
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27830
> ---
>  gdb/remote.c              | 99 ++++++++++++++++++++++++++-------------
>  gdbserver/remote-utils.cc | 26 ++++++++--
>  gdbserver/server.cc       |  3 +-
>  3 files changed, 91 insertions(+), 37 deletions(-)
>
> diff --git a/gdb/remote.c b/gdb/remote.c
> index 53c4f19c5a4..a7430eb79dd 100644
> --- a/gdb/remote.c
> +++ b/gdb/remote.c
> @@ -672,6 +672,7 @@ class remote_target : public process_stratum_target
>    const struct btrace_config *btrace_conf (const struct btrace_target_info *) override;
>    bool augmented_libraries_svr4_read () override;
>    void follow_fork (inferior *, ptid_t, target_waitkind, bool, bool) override;
> +  void follow_clone (ptid_t child_ptid) override;
>    void follow_exec (inferior *, ptid_t, const char *) override;
>    int insert_fork_catchpoint (int) override;
>    int remove_fork_catchpoint (int) override;
> @@ -765,7 +766,7 @@ class remote_target : public process_stratum_target
>  
>    void remote_btrace_maybe_reopen ();
>  
> -  void remove_new_fork_children (threads_listing_context *context);
> +  void remove_new_children (threads_listing_context *context);
>    void kill_new_fork_children (inferior *inf);
>    void discard_pending_stop_replies (struct inferior *inf);
>    int stop_reply_queue_length ();
> @@ -2579,9 +2580,10 @@ remote_target::remote_add_thread (ptid_t ptid, bool running, bool executing,
>    else
>      thread = add_thread (this, ptid);
>  
> -  /* We start by assuming threads are resumed.  That state then gets updated
> -     when we process a matching stop reply.  */
> -  get_remote_thread_info (thread)->set_resumed ();
> +  /* We start by assuming threads are resumed.  That state then gets
> +     updated when we process a matching stop reply.  */

If feels like that comment is now out of date.  We surely aren't
assuming anything anymore, rather marking the thread as resumed when its
executing.

Otherwise, this commit looks good.

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

Thanks,
Andrew

> +  if (executing)
> +    get_remote_thread_info (thread)->set_resumed ();
>  
>    set_executing (this, ptid, executing);
>    set_running (this, ptid, running);
> @@ -3983,10 +3985,11 @@ remote_target::update_thread_list ()
>  	    }
>  	}
>  
> -      /* Remove any unreported fork child threads from CONTEXT so
> -	 that we don't interfere with follow fork, which is where
> -	 creation of such threads is handled.  */
> -      remove_new_fork_children (&context);
> +      /* Remove any unreported fork/vfork/clone child threads from
> +	 CONTEXT so that we don't interfere with follow
> +	 fork/vfork/clone, which is where creation of such threads is
> +	 handled.  */
> +      remove_new_children (&context);
>  
>        /* And now add threads we don't know about yet to our list.  */
>        for (thread_item &item : context.items)
> @@ -4940,6 +4943,8 @@ remote_target::start_remote_1 (int from_tty, int extended_p)
>  	    }
>  	  else
>  	    switch_to_thread (find_thread_ptid (this, curr_thread));
> +
> +	  get_remote_thread_info (inferior_thread ())->set_resumed ();
>  	}
>  
>        /* init_wait_for_inferior should be called before get_offsets in order
> @@ -5893,16 +5898,25 @@ is_fork_status (target_waitkind kind)
>  	  || kind == TARGET_WAITKIND_VFORKED);
>  }
>  
> -/* Return THREAD's pending status if it is a pending fork parent, else
> -   return nullptr.  */
> +/* Return a reference to the field where a pending child status, if
> +   there's one, is recorded.  If there's no child event pending, the
> +   returned waitstatus has TARGET_WAITKIND_IGNORE kind.  */
> +
> +static const target_waitstatus &
> +thread_pending_status (struct thread_info *thread)
> +{
> +  return (thread->has_pending_waitstatus ()
> +	  ? thread->pending_waitstatus ()
> +	  : thread->pending_follow);
> +}
> +
> +/* Return THREAD's pending status if it is a pending fork/vfork (but
> +   not clone) parent, else return nullptr.  */
>  
>  static const target_waitstatus *
>  thread_pending_fork_status (struct thread_info *thread)
>  {
> -  const target_waitstatus &ws
> -    = (thread->has_pending_waitstatus ()
> -       ? thread->pending_waitstatus ()
> -       : thread->pending_follow);
> +  const target_waitstatus &ws = thread_pending_status (thread);
>  
>    if (!is_fork_status (ws.kind ()))
>      return nullptr;
> @@ -5910,6 +5924,20 @@ thread_pending_fork_status (struct thread_info *thread)
>    return &ws;
>  }
>  
> +/* Return THREAD's pending status if is is a pending fork/vfork/clone
> +   event, else return nullptr.  */
> +
> +static const target_waitstatus *
> +thread_pending_child_status (thread_info *thread)
> +{
> +  const target_waitstatus &ws = thread_pending_status (thread);
> +
> +  if (!is_new_child_status (ws.kind ()))
> +    return nullptr;
> +
> +  return &ws;
> +}
> +
>  /* Detach the specified process.  */
>  
>  void
> @@ -6075,6 +6103,12 @@ remote_target::follow_fork (inferior *child_inf, ptid_t child_ptid,
>      }
>  }
>  
> +void
> +remote_target::follow_clone (ptid_t child_ptid)
> +{
> +  remote_add_thread (child_ptid, false, false, false);
> +}
> +
>  /* Target follow-exec function for remote targets.  Save EXECD_PATHNAME
>     in the program space of the new inferior.  */
>  
> @@ -6807,10 +6841,10 @@ remote_target::commit_resumed ()
>        if (priv->get_resume_state () == resume_state::RESUMED_PENDING_VCONT)
>  	any_pending_vcont_resume = true;
>  
> -      /* If a thread is the parent of an unfollowed fork, then we
> -	 can't do a global wildcard, as that would resume the fork
> -	 child.  */
> -      if (thread_pending_fork_status (tp) != nullptr)
> +      /* If a thread is the parent of an unfollowed fork/vfork/clone,
> +	 then we can't do a global wildcard, as that would resume the
> +	 pending child.  */
> +      if (thread_pending_child_status (tp) != nullptr)
>  	may_global_wildcard_vcont = false;
>      }
>  
> @@ -7276,22 +7310,22 @@ struct notif_client notif_client_stop =
>    REMOTE_NOTIF_STOP,
>  };
>  
> -/* If CONTEXT contains any fork child threads that have not been
> -   reported yet, remove them from the CONTEXT list.  If such a
> -   thread exists it is because we are stopped at a fork catchpoint
> -   and have not yet called follow_fork, which will set up the
> -   host-side data structures for the new process.  */
> +/* If CONTEXT contains any fork/vfork/clone child threads that have
> +   not been reported yet, remove them from the CONTEXT list.  If such
> +   a thread exists it is because we are stopped at a fork/vfork/clone
> +   catchpoint and have not yet called follow_fork/follow_clone, which
> +   will set up the host-side data structures for the new child.  */
>  
>  void
> -remote_target::remove_new_fork_children (threads_listing_context *context)
> +remote_target::remove_new_children (threads_listing_context *context)
>  {
>    struct notif_client *notif = &notif_client_stop;
>  
> -  /* For any threads stopped at a fork event, remove the corresponding
> -     fork child threads from the CONTEXT list.  */
> +  /* For any threads stopped at a (v)fork/clone event, remove the
> +     corresponding child threads from the CONTEXT list.  */
>    for (thread_info *thread : all_non_exited_threads (this))
>      {
> -      const target_waitstatus *ws = thread_pending_fork_status (thread);
> +      const target_waitstatus *ws = thread_pending_child_status (thread);
>  
>        if (ws == nullptr)
>  	continue;
> @@ -7299,13 +7333,12 @@ remote_target::remove_new_fork_children (threads_listing_context *context)
>        context->remove_thread (ws->child_ptid ());
>      }
>  
> -  /* Check for any pending fork events (not reported or processed yet)
> -     in process PID and remove those fork child threads from the
> -     CONTEXT list as well.  */
> +  /* Check for any pending (v)fork/clone events (not reported or
> +     processed yet) in process PID and remove those child threads from
> +     the CONTEXT list as well.  */
>    remote_notif_get_pending_events (notif);
>    for (auto &event : get_remote_state ()->stop_reply_queue)
> -    if (event->ws.kind () == TARGET_WAITKIND_FORKED
> -	|| event->ws.kind () == TARGET_WAITKIND_VFORKED)
> +    if (is_new_child_status (event->ws.kind ()))
>        context->remove_thread (event->ws.child_ptid ());
>      else if (event->ws.kind () == TARGET_WAITKIND_THREAD_EXITED)
>        context->remove_thread (event->ptid);
> @@ -7634,6 +7667,8 @@ Packet: '%s'\n"),
>  	    event->ws.set_forked (read_ptid (++p1, &p));
>  	  else if (strprefix (p, p1, "vfork"))
>  	    event->ws.set_vforked (read_ptid (++p1, &p));
> +	  else if (strprefix (p, p1, "clone"))
> +	    event->ws.set_thread_cloned (read_ptid (++p1, &p));
>  	  else if (strprefix (p, p1, "vforkdone"))
>  	    {
>  	      event->ws.set_vfork_done ();
> diff --git a/gdbserver/remote-utils.cc b/gdbserver/remote-utils.cc
> index 2ddb275bd15..6a673cb1ca8 100644
> --- a/gdbserver/remote-utils.cc
> +++ b/gdbserver/remote-utils.cc
> @@ -1062,6 +1062,7 @@ prepare_resume_reply (char *buf, ptid_t ptid, const target_waitstatus &status)
>      case TARGET_WAITKIND_FORKED:
>      case TARGET_WAITKIND_VFORKED:
>      case TARGET_WAITKIND_VFORK_DONE:
> +    case TARGET_WAITKIND_THREAD_CLONED:
>      case TARGET_WAITKIND_EXECD:
>      case TARGET_WAITKIND_THREAD_CREATED:
>      case TARGET_WAITKIND_SYSCALL_ENTRY:
> @@ -1071,13 +1072,30 @@ prepare_resume_reply (char *buf, ptid_t ptid, const target_waitstatus &status)
>  	struct regcache *regcache;
>  	char *buf_start = buf;
>  
> -	if ((status.kind () == TARGET_WAITKIND_FORKED && cs.report_fork_events)
> +	if ((status.kind () == TARGET_WAITKIND_FORKED
> +	     && cs.report_fork_events)
>  	    || (status.kind () == TARGET_WAITKIND_VFORKED
> -		&& cs.report_vfork_events))
> +		&& cs.report_vfork_events)
> +	    || status.kind () == TARGET_WAITKIND_THREAD_CLONED)
>  	  {
>  	    enum gdb_signal signal = GDB_SIGNAL_TRAP;
> -	    const char *event = (status.kind () == TARGET_WAITKIND_FORKED
> -				 ? "fork" : "vfork");
> +
> +	    auto kind_remote_str = [] (target_waitkind kind)
> +	    {
> +	      switch (kind)
> +		{
> +		case TARGET_WAITKIND_FORKED:
> +		  return "fork";
> +		case TARGET_WAITKIND_VFORKED:
> +		  return "vfork";
> +		case TARGET_WAITKIND_THREAD_CLONED:
> +		  return "clone";
> +		default:
> +		  gdb_assert_not_reached ("unhandled kind");
> +		}
> +	    };
> +
> +	    const char *event = kind_remote_str (status.kind ());
>  
>  	    sprintf (buf, "T%02x%s:", signal, event);
>  	    buf += strlen (buf);
> diff --git a/gdbserver/server.cc b/gdbserver/server.cc
> index aaef38e0062..56b7f97a388 100644
> --- a/gdbserver/server.cc
> +++ b/gdbserver/server.cc
> @@ -236,7 +236,8 @@ in_queued_stop_replies_ptid (struct notif_event *event, ptid_t filter_ptid)
>  
>    /* Don't resume fork children that GDB does not know about yet.  */
>    if ((vstop_event->status.kind () == TARGET_WAITKIND_FORKED
> -       || vstop_event->status.kind () == TARGET_WAITKIND_VFORKED)
> +       || vstop_event->status.kind () == TARGET_WAITKIND_VFORKED
> +       || vstop_event->status.kind () == TARGET_WAITKIND_THREAD_CLONED)
>        && vstop_event->status.child_ptid ().matches (filter_ptid))
>      return true;
>  
> -- 
> 2.36.0


  reply	other threads:[~2023-03-22 15:46 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
2023-03-10 17:15     ` Pedro Alves
2023-03-16 16:07       ` Andrew Burgess
2023-03-22 21:29         ` Andrew Burgess
2023-03-23 15:15           ` Pedro Alves
2023-03-27 12:40             ` Andrew Burgess
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
2023-03-10 17:15     ` Pedro Alves
2023-03-16 16:19       ` Andrew Burgess
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
2023-04-04 13:57     ` Pedro Alves
2023-04-14 19:29       ` Pedro Alves
2023-05-26 15:04         ` Andrew Burgess
2023-11-13 14:04           ` Pedro Alves
2023-05-26 14:45       ` Andrew Burgess
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
2023-03-10 17:16     ` Pedro Alves
2023-03-21 16:06       ` Andrew Burgess
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 [this message]
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
2022-12-12 20:30 ` [PATCH 07/31] enum_flags to_string Pedro Alves
2023-01-30 20:07   ` Simon Marchi
2022-12-12 20:30 ` [PATCH 08/31] Thread options & clone events (core + remote) Pedro Alves
2023-01-31 12:25   ` Lancelot SIX
2023-03-10 19:16     ` Pedro Alves
2023-06-06 13:29       ` Andrew Burgess
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
2022-12-12 20:30 ` [PATCH 10/31] Thread options & clone events (Linux GDBserver) Pedro Alves
2023-06-06 14:12   ` Andrew Burgess
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
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
2022-12-12 20:30 ` [PATCH 13/31] Add test for stepping over clone syscall Pedro Alves
2023-06-07 17:42   ` Andrew Burgess
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
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
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
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
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
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
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
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
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
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
2022-12-12 20:30 ` [PATCH 25/31] Ignore failure to read PC when resuming Pedro Alves
2023-06-10 10:33   ` Andrew Burgess
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
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
2022-12-12 20:30 ` [PATCH 28/31] Document remote clone events, and QThreadOptions packet Pedro Alves
2023-06-05 15:53   ` Andrew Burgess
2023-11-13 14:13     ` Pedro Alves
2023-06-12 12:06   ` Andrew Burgess
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
2022-12-12 20:31 ` [PATCH 30/31] Centralize "[Thread ...exited]" notifications Pedro Alves
2023-02-04 16:05   ` Andrew Burgess
2023-03-10 17:21     ` Pedro Alves
2023-02-16 15:40   ` Andrew Burgess
2023-06-12 12:23     ` Andrew Burgess
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
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=87cz50dc1y.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).