Date: Tue, 5 Jun 2012 11:52:02 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Steve Wills <swills@freebsd.org> Cc: ports@freebsd.org, ruby@freebsd.org Subject: Re: Ruby 1.9 as default Message-ID: <20120605085202.GI85127@deviant.kiev.zoral.com.ua> In-Reply-To: <4FCD51E4.4030309@FreeBSD.org> References: <4FC96D45.8080904@FreeBSD.org> <20120601193059.af9201da.stas@FreeBSD.org> <4FCD51E4.4030309@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--FUFe+yI/t+r3nyH4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 04, 2012 at 08:25:08PM -0400, Steve Wills wrote: > On 06/01/12 22:30, Stanislav Sedov wrote: > >=20 > > I'm not sure it's a good idea. > > Ruby 1.9 still has some nasty bugs on FreeBSD, related to the threads a= nd > > fork. That is fork in ruby 1.9 hangs sometimes... >=20 > The ONLY thing I can find is this: >=20 > http://bugs.ruby-lang.org/issues/2097 >=20 > which implies that it's fixed. If there's more to this issue than > "broken on 7.3 and earlier", PLEASE let me know. If ruby indeed does what the bugs described, that is, calls non-async signal safe functions from the threaded process after fork, then you are guaranteed to get random hangs sometimes. --FUFe+yI/t+r3nyH4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/NyLIACgkQC3+MBN1Mb4jZZQCfZblZW/QslxLHdXJN0sxmKUzC HvUAoItXJqr4XFwVkG+7GLY7noS3TP+T =6iuj -----END PGP SIGNATURE----- --FUFe+yI/t+r3nyH4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120605085202.GI85127>