From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 00/11] Linux: Fix issues around thread group leader exits
Date: Thu, 3 Mar 2022 14:40:09 +0000 [thread overview]
Message-ID: <20220303144020.3601082-1-pedro@palves.net> (raw)
This series addresses some problems around thread group leader exits
on GNU/Linux (native and gdbserver):
- addresses a race in zombie leader detection
- make sure only the leader's exit status is interpreted as whole-process exit status
- make sure the whole-process exit is always the last event reported
Tested on GNU/Linux x86-64, native and extended-remote gdbserver. New
testcase added at the end of the series.
Lancelot SIX (2):
Ensure EXIT is last event, gdb/linux
Process exit status is leader exit status testcase
Pedro Alves (9):
Fix gdbserver/linux target_waitstatus logging assert
Fix gdb.threads/clone-new-thread-event.exp race
Fix gdb.threads/current-lwp-dead.exp race
gdb: Reorganize linux_nat_filter_event
gdbserver: Reorganize linux_process_target::filter_event
gdbserver: Reindent check_zombie_leaders
Re-add zombie leader on exit, gdb/linux
Re-add zombie leader on exit, gdbserver/linux
Ensure EXIT is last event, gdbserver/linux
gdb/linux-nat.c | 226 ++++++++++----
.../gdb.threads/clone-new-thread-event.c | 16 +-
.../gdb.threads/clone-new-thread-event.exp | 2 +
gdb/testsuite/gdb.threads/current-lwp-dead.c | 101 ++++---
.../gdb.threads/current-lwp-dead.exp | 23 +-
...rocess-exit-status-is-leader-exit-status.c | 64 ++++
...cess-exit-status-is-leader-exit-status.exp | 45 +++
gdbserver/linux-low.cc | 281 +++++++++++-------
gdbserver/linux-low.h | 15 +-
9 files changed, 563 insertions(+), 210 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/process-exit-status-is-leader-exit-status.c
create mode 100644 gdb/testsuite/gdb.threads/process-exit-status-is-leader-exit-status.exp
base-commit: c2b167b3d601dd20de0640e2fbd46835599a1537
--
2.26.2
next reply other threads:[~2022-03-03 14:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 14:40 Pedro Alves [this message]
2022-03-03 14:40 ` [PATCH 01/11] Fix gdbserver/linux target_waitstatus logging assert Pedro Alves
2022-03-03 14:40 ` [PATCH 02/11] Fix gdb.threads/clone-new-thread-event.exp race Pedro Alves
2022-03-03 14:40 ` [PATCH 03/11] Fix gdb.threads/current-lwp-dead.exp race Pedro Alves
2022-03-03 14:40 ` [PATCH 04/11] gdb: Reorganize linux_nat_filter_event Pedro Alves
2022-03-03 14:40 ` [PATCH 05/11] gdbserver: Reorganize linux_process_target::filter_event Pedro Alves
2022-03-03 14:40 ` [PATCH 06/11] gdbserver: Reindent check_zombie_leaders Pedro Alves
2022-03-03 14:40 ` [PATCH 07/11] Re-add zombie leader on exit, gdb/linux Pedro Alves
2022-03-07 20:08 ` Simon Marchi
2022-03-07 20:27 ` Pedro Alves
2022-03-07 20:31 ` Simon Marchi
2022-03-09 14:37 ` Pedro Alves
2022-03-03 14:40 ` [PATCH 08/11] Re-add zombie leader on exit, gdbserver/linux Pedro Alves
2022-03-03 14:40 ` [PATCH 09/11] Ensure EXIT is last event, gdb/linux Pedro Alves
2022-03-07 20:24 ` Simon Marchi
2022-03-09 0:21 ` Lancelot SIX
2022-03-09 14:45 ` Pedro Alves
2022-03-09 22:29 ` Lancelot SIX
2022-03-10 11:46 ` Pedro Alves
2022-03-03 14:40 ` [PATCH 10/11] Ensure EXIT is last event, gdbserver/linux Pedro Alves
2022-03-03 14:40 ` [PATCH 11/11] Process exit status is leader exit status testcase Pedro Alves
2023-06-22 11:28 ` Ilya Leoshkevich
2023-06-22 13:07 ` Tom de Vries
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=20220303144020.3601082-1-pedro@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
/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).