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 11/31] gdbserver: Hide and don't detach pending clone children
Date: Wed, 07 Jun 2023 17:10:58 +0100	[thread overview]
Message-ID: <878rcv1cdp.fsf@redhat.com> (raw)
In-Reply-To: <20221212203101.1034916-12-pedro@palves.net>

Pedro Alves <pedro@palves.net> writes:

> This commit extends the logic added by these two commits from a while
> ago:
>
>  #1  7b961964f866  (gdbserver: hide fork child threads from GDB),
>  #2  df5ad102009c  (gdb, gdbserver: detach fork child when detaching from fork parent)
>
> ... to handle thread clone events, which are very similar to (v)fork
> events.
>
> For #1, we want to hide clone children as well, so just update the
> comments.
>
> For #2, unlike (v)fork children, pending clone children aren't full
> processes, they're just threads, so don't detach them in
> handle_detach.  linux-low.cc will take care of detaching them along
> with all other threads of the process, there's nothing special that
> needs to be done.
>
> Change-Id: I7f5901d07efda576a2522d03e183994e071b8ffc
> ---
>  gdbserver/linux-low.cc |  5 +++--
>  gdbserver/linux-low.h  | 36 ++++++++++++++++++++----------------
>  gdbserver/server.cc    | 12 +++++++-----
>  gdbserver/target.cc    |  3 ++-
>  gdbserver/target.h     | 15 ++++++++-------
>  5 files changed, 40 insertions(+), 31 deletions(-)
>
> diff --git a/gdbserver/linux-low.cc b/gdbserver/linux-low.cc
> index d755cda0e44..a7c310260ca 100644
> --- a/gdbserver/linux-low.cc
> +++ b/gdbserver/linux-low.cc
> @@ -6940,9 +6940,10 @@ linux_process_target::thread_pending_parent (thread_info *thread)
>  }
>  
>  thread_info *
> -linux_process_target::thread_pending_child (thread_info *thread)
> +linux_process_target::thread_pending_child (thread_info *thread,
> +					    target_waitkind *kind)
>  {
> -  lwp_info *child = get_thread_lwp (thread)->pending_child ();
> +  lwp_info *child = get_thread_lwp (thread)->pending_child (kind);
>  
>    if (child == nullptr)
>      return nullptr;
> diff --git a/gdbserver/linux-low.h b/gdbserver/linux-low.h
> index 69a34fb96fc..c9f9db71e09 100644
> --- a/gdbserver/linux-low.h
> +++ b/gdbserver/linux-low.h
> @@ -315,7 +315,8 @@ class linux_process_target : public process_stratum_target
>  #endif
>  
>    thread_info *thread_pending_parent (thread_info *thread) override;
> -  thread_info *thread_pending_child (thread_info *thread) override;
> +  thread_info *thread_pending_child (thread_info *thread,
> +				     target_waitkind *kind) override;
>  
>    bool supports_catch_syscall () override;
>  
> @@ -734,8 +735,8 @@ struct pending_signal
>  
>  struct lwp_info
>  {
> -  /* If this LWP is a fork child that wasn't reported to GDB yet, return
> -     its parent, else nullptr.  */
> +  /* If this LWP is a fork/vfork/clone child that wasn't reported to
> +     GDB yet, return its parent, else nullptr.  */
>    lwp_info *pending_parent () const
>    {
>      if (this->fork_relative == nullptr)
> @@ -743,10 +744,10 @@ struct lwp_info
>  
>      gdb_assert (this->fork_relative->fork_relative == this);
>  
> -    /* In a fork parent/child relationship, the parent has a status pending and
> -       the child does not, and a thread can only be in one such relationship
> -       at most.  So we can recognize who is the parent based on which one has
> -       a pending status.  */
> +    /* In a parent/child relationship, the parent has a status pending
> +       and the child does not, and a thread can only be in one such
> +       relationship at most.  So we can recognize who is the parent
> +       based on which one has a pending status.  */
>      gdb_assert (!!this->status_pending_p
>  		!= !!this->fork_relative->status_pending_p);
>  
> @@ -756,24 +757,25 @@ struct lwp_info
>      const target_waitstatus &ws
>        = this->fork_relative->waitstatus;
>      gdb_assert (ws.kind () == TARGET_WAITKIND_FORKED
> -		|| ws.kind () == TARGET_WAITKIND_VFORKED);
> +		|| ws.kind () == TARGET_WAITKIND_VFORKED
> +		|| ws.kind () == TARGET_WAITKIND_THREAD_CLONED);
>  
>      return this->fork_relative;
>    }
>  
> -  /* If this LWP is the parent of a fork child we haven't reported to GDB yet,
> -     return that child, else nullptr.  */
> -  lwp_info *pending_child () const
> +  /* If this LWP is the parent of a fork/vfork/clone child we haven't
> +     reported to GDB yet, return that child, else nullptr.  */
> +  lwp_info *pending_child (target_waitkind *kind) const
>    {
>      if (this->fork_relative == nullptr)
>        return nullptr;
>  
>      gdb_assert (this->fork_relative->fork_relative == this);
>  
> -    /* In a fork parent/child relationship, the parent has a status pending and
> -       the child does not, and a thread can only be in one such relationship
> -       at most.  So we can recognize who is the parent based on which one has
> -       a pending status.  */
> +    /* In a parent/child relationship, the parent has a status pending
> +       and the child does not, and a thread can only be in one such
> +       relationship at most.  So we can recognize who is the parent
> +       based on which one has a pending status.  */
>      gdb_assert (!!this->status_pending_p
>  		!= !!this->fork_relative->status_pending_p);
>  
> @@ -782,8 +784,10 @@ struct lwp_info
>  
>      const target_waitstatus &ws = this->waitstatus;
>      gdb_assert (ws.kind () == TARGET_WAITKIND_FORKED
> -		|| ws.kind () == TARGET_WAITKIND_VFORKED);
> +		|| ws.kind () == TARGET_WAITKIND_VFORKED
> +		|| ws.kind () == TARGET_WAITKIND_THREAD_CLONED);
>  
> +    *kind = ws.kind ();
>      return this->fork_relative;
>    }
>  
> diff --git a/gdbserver/server.cc b/gdbserver/server.cc
> index 5b07c4e4388..07a3319d114 100644
> --- a/gdbserver/server.cc
> +++ b/gdbserver/server.cc
> @@ -1344,8 +1344,9 @@ handle_detach (char *own_buf)
>  	continue;
>  
>        /* Only threads that have a pending fork event.  */
> -      thread_info *child = target_thread_pending_child (thread);
> -      if (child == nullptr)
> +      target_waitkind kind;
> +      thread_info *child = target_thread_pending_child (thread, &kind);
> +      if (child == nullptr || kind == TARGET_WAITKIND_THREAD_CLONED)
>  	continue;
>  
>        process_info *fork_child_process = get_thread_process (child);
> @@ -1765,9 +1766,10 @@ handle_qxfer_threads_worker (thread_info *thread, struct buffer *buffer)
>    gdb_byte *handle;
>    bool handle_status = target_thread_handle (ptid, &handle, &handle_len);
>  
> -  /* If this is a fork or vfork child (has a fork parent), GDB does not yet
> -     know about this process, and must not know about it until it gets the
> -     corresponding (v)fork event.  Exclude this thread from the list.  */
> +  /* If this is a (v)fork/clone child (has a (v)fork/clone parent),
> +     GDB does not yet know about this thread, and must not know about
> +     it until it gets the corresponding (v)fork/clone event.  Exclude
> +     this thread from the list.  */
>    if (target_thread_pending_parent (thread) != nullptr)
>      return;
>  
> diff --git a/gdbserver/target.cc b/gdbserver/target.cc
> index 168b843d2ec..4584e9b3a8e 100644
> --- a/gdbserver/target.cc
> +++ b/gdbserver/target.cc
> @@ -814,7 +814,8 @@ process_stratum_target::thread_pending_parent (thread_info *thread)
>  }
>  
>  thread_info *
> -process_stratum_target::thread_pending_child (thread_info *thread)
> +process_stratum_target::thread_pending_child (thread_info *thread,
> +					      target_waitkind *kind)
>  {
>    return nullptr;
>  }
> diff --git a/gdbserver/target.h b/gdbserver/target.h
> index 8a0d9f42f7d..e2e818b130b 100644
> --- a/gdbserver/target.h
> +++ b/gdbserver/target.h
> @@ -479,13 +479,14 @@ class process_stratum_target
>    virtual bool thread_handle (ptid_t ptid, gdb_byte **handle,
>  			      int *handle_len);
>  
> -  /* If THREAD is a fork child that was not reported to GDB, return its parent
> -     else nullptr.  */
> +  /* If THREAD is a fork/vfork/clone child that was not reported to
> +     GDB, return its parent else nullptr.  */
>    virtual thread_info *thread_pending_parent (thread_info *thread);
>  
> -  /* If THREAD is the parent of a fork child that was not reported to GDB,
> -     return this child, else nullptr.  */
> -  virtual thread_info *thread_pending_child (thread_info *thread);
> +  /* If THREAD is the parent of a fork/vfork/clone child that was not
> +     reported to GDB, return this child, else nullptr.  */
> +  virtual thread_info *thread_pending_child (thread_info *thread,
> +					     target_waitkind *kind);

Should the comment not say what happens to KIND?  I think this comment
applies throughout this patch where KIND was added as an argument.

Otherwise, this looks good.

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

Thanks,
Andrew

>  
>    /* Returns true if the target can software single step.  */
>    virtual bool supports_software_single_step ();
> @@ -701,9 +702,9 @@ target_thread_pending_parent (thread_info *thread)
>  }
>  
>  static inline thread_info *
> -target_thread_pending_child (thread_info *thread)
> +target_thread_pending_child (thread_info *thread, target_waitkind *kind)
>  {
> -  return the_target->thread_pending_child (thread);
> +  return the_target->thread_pending_child (thread, kind);
>  }
>  
>  int read_inferior_memory (CORE_ADDR memaddr, unsigned char *myaddr, int len);
> -- 
> 2.36.0


  reply	other threads:[~2023-06-07 16:11 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
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 [this message]
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=878rcv1cdp.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).