-
Notifications
You must be signed in to change notification settings - Fork 20
On macOS >= 12, don't use vfork(2) #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Addresses #34. |
cfd1373
to
956c91f
Compare
8a85852
to
c3be198
Compare
41f2e63
to
6e02a7b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is sad because fork is slow, but I don't have any better idea.
It's deprecated. Use fork(2) instead. Signed-off-by: Jesse A. Tov <jesse.tov@gmail.com>
vfork(2) is deprecated on macOS 12, so we need to test on both. Signed-off-by: Jesse Tov <jtov@janestreet.com>
Maybe #47 is preferable? |
On recent versions of Macos, vfork is just aliased to fork. So I would welcome this PR to disable vfork on macos completely |
Because I can't figure out how to run the CI without making a change. Signed-off-by: Jesse A. Tov <jesse.tov@gmail.com>
vfork(2) is deprecated on macOS >= 12, so we need to use fork(2) instead to avoid deprecation warnings. (Should we use posix_spawn(2) where available?)