From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Add "real" vfork done handling on FreeBSD
Date: Mon, 18 Jul 2016 14:58:00 -0000 [thread overview]
Message-ID: <20160718145759.58543-1-jhb@FreeBSD.org> (raw)
FreeBSD 12 recently gained a real vfork done event via ptrace(2).
This changes the FreeBSD native targets to use this when it exists
instead of faking a done event after a sleep.
John Baldwin (3):
Consolidate code to enable optional FreeBSD native target event
reporting.
Enable ptrace events on new child processes.
Use a real vfork done event on FreeBSD when available.
gdb/ChangeLog | 31 ++++++++++++++++++++
gdb/fbsd-nat.c | 92 ++++++++++++++++++++++++++++++++++++----------------------
2 files changed, 89 insertions(+), 34 deletions(-)
--
2.8.4
next reply other threads:[~2016-07-18 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:58 John Baldwin [this message]
2016-07-18 14:58 ` [PATCH 3/3] Use a real vfork done event on FreeBSD when available John Baldwin
2016-07-18 14:58 ` [PATCH 2/3] Enable ptrace events on new child processes John Baldwin
2016-07-18 14:58 ` [PATCH 1/3] Consolidate code to enable optional FreeBSD native target event reporting John Baldwin
2016-07-19 18:44 ` [PATCH 0/3] Add "real" vfork done handling on FreeBSD 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=20160718145759.58543-1-jhb@FreeBSD.org \
--to=jhb@freebsd.org \
--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