From: Tom Tromey <tom@tromey.com>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Simon Marchi <simark@simark.ca>, Enze Li <enze.li@hotmail.com>,
gdb-patches@sourceware.org, enze.li@gmx.com
Subject: Re: [PATCH] gdb: fix -Wdeprecated-declarations on macOS
Date: Tue, 28 Mar 2023 09:57:17 -0600 [thread overview]
Message-ID: <87cz4sdg2q.fsf@tromey.com> (raw)
In-Reply-To: <7657bb99-0319-ed79-fe2a-fb74a3876798@FreeBSD.org> (John Baldwin's message of "Tue, 28 Mar 2023 08:10:02 -0700")
>>>>> "John" == John Baldwin <jhb@FreeBSD.org> writes:
John> Even if vfork is deprecated, you still want to use it instead of fork I think
John> as long as it exists. The real fix is to add a patch to use posix_spawn
John> to fork the shell instead of vfork when posix_spawn exists. posix_spawn is
John> just a wrapper around vfork + execve on FreeBSD's libc for example (I haven't
John> looked to see what it is on Linux but suspect it is similar).
I'm not sure we can do this in fork-inferior due to the need to
PTRACE_TRACEME in the child.
The other cases could maybe use the PEX stuff from libiberty?
Tom
next prev parent reply other threads:[~2023-03-28 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 14:16 Enze Li
2023-03-28 14:55 ` Simon Marchi
2023-03-28 15:10 ` John Baldwin
2023-03-28 15:57 ` Tom Tromey [this message]
2023-03-28 16:01 ` Simon Marchi
2023-03-28 17:52 ` John Baldwin
2023-03-28 17:57 ` John Baldwin
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=87cz4sdg2q.fsf@tromey.com \
--to=tom@tromey.com \
--cc=enze.li@gmx.com \
--cc=enze.li@hotmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=simark@simark.ca \
/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).