From: Simon Marchi <simon.marchi@polymtl.ca>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/9] Some fixes for handling vfork by multi-threaded programs
Date: Mon, 17 Jan 2022 23:09:28 -0500 [thread overview]
Message-ID: <20220118040937.730282-1-simon.marchi@polymtl.ca> (raw)
This is v2 of:
https://sourceware.org/pipermail/gdb-patches/2022-January/185204.html
The two changes are:
- New patch 8: patch 7 fixes a bug gdbserver-side, which is good, but
it then uncovers a small bug in gdb. Patch 8 fixes it.
- Patch 8/8 in v1 (now 9/9) had a bug that broke some tests that detach
the fork parent.
Simon Marchi (9):
gdb/infrun: add reason parameter to stop_all_threads
gdb/linux-nat: remove check based on current_inferior in
linux_handle_extended_wait
gdb: replace inferior::waiting_for_vfork_done with
inferior::thread_waiting_for_vfork_done
gdb/infrun: add inferior parameters to stop_all_threads and
restart_threads
gdb/infrun: add logging statement to do_target_resume
gdb: fix handling of vfork by multi-threaded program
(follow-fork-mode=parent, detach-on-fork=on)
gdbserver: report correct status in thread stop race condition
gdb/remote: remove_new_fork_children don't access
target_waitstatus::child_ptid if kind ==
TARGET_WAITKIND_THREAD_EXITED
gdb: resume ongoing step after handling fork or vfork
gdb/infcmd.c | 2 +-
gdb/inferior.h | 8 +-
gdb/infrun.c | 212 ++++++++++++++++--
gdb/infrun.h | 14 +-
gdb/linux-nat.c | 17 +-
gdb/remote.c | 7 +-
.../gdb.threads/next-fork-other-thread.c | 86 +++++++
.../gdb.threads/next-fork-other-thread.exp | 116 ++++++++++
.../gdb.threads/vfork-multi-inferior-sleep.c | 25 +++
.../gdb.threads/vfork-multi-inferior.c | 55 +++++
.../gdb.threads/vfork-multi-inferior.exp | 115 ++++++++++
.../gdb.threads/vfork-multi-thread.c | 74 ++++++
.../gdb.threads/vfork-multi-thread.exp | 96 ++++++++
gdbserver/linux-low.cc | 60 +++--
14 files changed, 806 insertions(+), 81 deletions(-)
create mode 100644 gdb/testsuite/gdb.threads/next-fork-other-thread.c
create mode 100644 gdb/testsuite/gdb.threads/next-fork-other-thread.exp
create mode 100644 gdb/testsuite/gdb.threads/vfork-multi-inferior-sleep.c
create mode 100644 gdb/testsuite/gdb.threads/vfork-multi-inferior.c
create mode 100644 gdb/testsuite/gdb.threads/vfork-multi-inferior.exp
create mode 100644 gdb/testsuite/gdb.threads/vfork-multi-thread.c
create mode 100644 gdb/testsuite/gdb.threads/vfork-multi-thread.exp
base-commit: e2c0149e8b0ce12accb8f4b02cbbeff3e91e4737
--
2.34.1
next reply other threads:[~2022-01-18 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 4:09 Simon Marchi [this message]
2022-01-18 4:09 ` [PATCH v2 1/9] gdb/infrun: add reason parameter to stop_all_threads Simon Marchi
2022-01-18 4:09 ` [PATCH v2 2/9] gdb/linux-nat: remove check based on current_inferior in linux_handle_extended_wait Simon Marchi
2022-01-18 4:09 ` [PATCH v2 3/9] gdb: replace inferior::waiting_for_vfork_done with inferior::thread_waiting_for_vfork_done Simon Marchi
2022-01-18 4:09 ` [PATCH v2 4/9] gdb/infrun: add inferior parameters to stop_all_threads and restart_threads Simon Marchi
2022-01-18 4:09 ` [PATCH v2 5/9] gdb/infrun: add logging statement to do_target_resume Simon Marchi
2022-01-18 4:09 ` [PATCH v2 6/9] gdb: fix handling of vfork by multi-threaded program (follow-fork-mode=parent, detach-on-fork=on) Simon Marchi
2022-02-16 0:28 ` Lancelot SIX
2022-02-16 13:35 ` Simon Marchi
2022-01-18 4:09 ` [PATCH v2 7/9] gdbserver: report correct status in thread stop race condition Simon Marchi
2022-01-18 4:09 ` [PATCH v2 8/9] gdb/remote: remove_new_fork_children don't access target_waitstatus::child_ptid if kind == TARGET_WAITKIND_THREAD_EXITED Simon Marchi
2022-03-31 19:25 ` Pedro Alves
2022-01-18 4:09 ` [PATCH v2 9/9] gdb: resume ongoing step after handling fork or vfork Simon Marchi
2022-03-31 19:28 ` Pedro Alves
2022-03-23 13:02 ` [PATCH v2 0/9] Some fixes for handling vfork by multi-threaded programs Simon Marchi
2022-04-05 2:13 ` Simon Marchi
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=20220118040937.730282-1-simon.marchi@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--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).