From: Andrew Burgess <aburgess@redhat.com>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 18/31] Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver
Date: Thu, 08 Jun 2023 15:14:57 +0100 [thread overview]
Message-ID: <87o7lqyra6.fsf@redhat.com> (raw)
In-Reply-To: <20221212203101.1034916-19-pedro@palves.net>
Pedro Alves <pedro@palves.net> writes:
> This implements support for the new GDB_THREAD_OPTION_EXIT thread
> option for Linux GDBserver.
LGTM.
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Thanks,
Andrew
>
> Change-Id: I96b719fdf7fee94709e98bb3a90751d8134f3a38
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27338
> ---
> gdbserver/linux-low.cc | 38 +++++++++++++++++++++++++-------------
> gdbserver/linux-low.h | 9 +++++----
> 2 files changed, 30 insertions(+), 17 deletions(-)
>
> diff --git a/gdbserver/linux-low.cc b/gdbserver/linux-low.cc
> index 8c0d3103398..ebc3bf34127 100644
> --- a/gdbserver/linux-low.cc
> +++ b/gdbserver/linux-low.cc
> @@ -144,6 +144,18 @@ is_leader (thread_info *thread)
> return ptid.pid () == ptid.lwp ();
> }
>
> +/* Return true if we should report thread exit events to GDB, for
> + THR. */
> +
> +static bool
> +report_exit_events_for (thread_info *thr)
> +{
> + client_state &cs = get_client_state ();
> +
> + return (cs.report_thread_events
> + || (thr->thread_options & GDB_THREAD_OPTION_EXIT) != 0);
> +}
> +
> /* LWP accessors. */
>
> /* See nat/linux-nat.h. */
> @@ -2230,7 +2242,6 @@ linux_low_ptrace_options (int attached)
> void
> linux_process_target::filter_event (int lwpid, int wstat)
> {
> - client_state &cs = get_client_state ();
> struct lwp_info *child;
> struct thread_info *thread;
> int have_stop_pc = 0;
> @@ -2317,7 +2328,7 @@ linux_process_target::filter_event (int lwpid, int wstat)
> /* If this is not the leader LWP, then the exit signal was not
> the end of the debugged application and should be ignored,
> unless GDB wants to hear about thread exits. */
> - if (cs.report_thread_events || is_leader (thread))
> + if (report_exit_events_for (thread) || is_leader (thread))
> {
> /* Since events are serialized to GDB core, and we can't
> report this one right now. Leave the status pending for
> @@ -2879,13 +2890,20 @@ ptid_t
> linux_process_target::filter_exit_event (lwp_info *event_child,
> target_waitstatus *ourstatus)
> {
> - client_state &cs = get_client_state ();
> struct thread_info *thread = get_lwp_thread (event_child);
> ptid_t ptid = ptid_of (thread);
>
> + /* Note we must filter TARGET_WAITKIND_SIGNALLED as well, otherwise
> + if a non-leader thread exits with a signal, we'd report it to the
> + core which would interpret it as the whole-process exiting.
> + There is no TARGET_WAITKIND_THREAD_SIGNALLED event kind. */
> + if (ourstatus->kind () != TARGET_WAITKIND_EXITED
> + && ourstatus->kind () != TARGET_WAITKIND_SIGNALLED)
> + return ptid;
> +
> if (!is_leader (thread))
> {
> - if (cs.report_thread_events)
> + if (report_exit_events_for (thread))
> ourstatus->set_thread_exited (0);
> else
> ourstatus->set_ignore ();
> @@ -3028,10 +3046,7 @@ linux_process_target::wait_1 (ptid_t ptid, target_waitstatus *ourstatus,
> WTERMSIG (w));
> }
>
> - if (ourstatus->kind () == TARGET_WAITKIND_EXITED)
> - return filter_exit_event (event_child, ourstatus);
> -
> - return ptid_of (current_thread);
> + return filter_exit_event (event_child, ourstatus);
> }
>
> /* If step-over executes a breakpoint instruction, in the case of a
> @@ -3600,10 +3615,7 @@ linux_process_target::wait_1 (ptid_t ptid, target_waitstatus *ourstatus,
> target_pid_to_str (ptid_of (current_thread)).c_str (),
> ourstatus->to_string ().c_str ());
>
> - if (ourstatus->kind () == TARGET_WAITKIND_EXITED)
> - return filter_exit_event (event_child, ourstatus);
> -
> - return ptid_of (current_thread);
> + return filter_exit_event (event_child, ourstatus);
> }
>
> /* Get rid of any pending event in the pipe. */
> @@ -5909,7 +5921,7 @@ linux_process_target::supports_vfork_events ()
> gdb_thread_options
> linux_process_target::supported_thread_options ()
> {
> - return GDB_THREAD_OPTION_CLONE;
> + return GDB_THREAD_OPTION_CLONE | GDB_THREAD_OPTION_EXIT;
> }
>
> /* Check if exec events are supported. */
> diff --git a/gdbserver/linux-low.h b/gdbserver/linux-low.h
> index c9f9db71e09..1c1754d2b59 100644
> --- a/gdbserver/linux-low.h
> +++ b/gdbserver/linux-low.h
> @@ -575,10 +575,11 @@ class linux_process_target : public process_stratum_target
> exited. */
> void check_zombie_leaders ();
>
> - /* Convenience function that is called when the kernel reports an exit
> - event. This decides whether to report the event to GDB as a
> - process exit event, a thread exit event, or to suppress the
> - event. */
> + /* Convenience function that is called when we're about to return an
> + event to the core. If the event is an exit or signalled event,
> + then this decides whether to report it as process-wide event, as
> + a thread exit event, or to suppress it. All other event kinds
> + are passed through unmodified. */
> ptid_t filter_exit_event (lwp_info *event_child,
> target_waitstatus *ourstatus);
>
> --
> 2.36.0
next prev parent reply other threads:[~2023-06-08 14:15 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
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 [this message]
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=87o7lqyra6.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).