unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Jeffrey Carl Faden <jeffreyatw@gmail.com>
Cc: unicorn-public@bogomips.org
Subject: Re: initialize/fork crash in macOS 10.13
Date: Fri, 4 Aug 2017 19:10:23 +0000	[thread overview]
Message-ID: <20170804191023.GA28511@dcvr> (raw)
In-Reply-To: <F28C7A88-7048-47A4-9B31-1D4AA128604D@gmail.com>

Jeffrey Carl Faden <jeffreyatw@gmail.com> wrote:
> According to this post...
> http://www.sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html
> The rules around initialize and fork() have changed in macOS
> 10.13, which is coming out in a month or so. I tried using
> Unicorn today to run a unicorn_rails instance, and got this as
> part of my traceback:

This affects other Ruby programs which fork().  I suggest
reporting to ruby-core @ https://bugs.ruby-lang.org/ and having
somebody with macOS knowledge look at this(*).

I don't even know how ObjC factors into this.

> I'm not sure if this is something downstream, but I thought
> I'd bring it to your attention. My temporary solution is to
> preface my commands with

Thanks for documenting this for other users, at least.
I can't support macOS since I'm not allowed to know
everything about it.

(*) As a smug GNU/Linux user, I get to know EVERYTHING about how
    my system works from the kernel and up, for free!
    And when I do have a question I can't answer on my own;
    all I need to do is email the right people and lists.
    No NDAs or registration of any sort to deal with :>

  reply	other threads:[~2017-08-04 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-04 16:40 initialize/fork crash in macOS 10.13 Jeffrey Carl Faden
2017-08-04 19:10 ` Eric Wong [this message]
2017-10-16 19:25   ` Eric Wong

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:

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170804191023.GA28511@dcvr \
    --to=e@80x24.org \
    --cc=jeffreyatw@gmail.com \
    --cc=unicorn-public@bogomips.org \


* 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.
Code repositories for project(s) associated with this public inbox


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).