From owner-freebsd-ruby@FreeBSD.ORG Tue Jun 5 09:04:42 2012 Return-Path: Delivered-To: ruby@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93D31106566C; Tue, 5 Jun 2012 09:04:42 +0000 (UTC) (envelope-from stas@freebsd.org) Received: from mx0.deglitch.com (cl-414.sto-01.se.sixxs.net [IPv6:2001:16d8:ff00:19d::2]) by mx1.freebsd.org (Postfix) with ESMTP id 418358FC0C; Tue, 5 Jun 2012 09:04:42 +0000 (UTC) Received: from [192.168.1.118] (c-98-234-105-176.hsd1.ca.comcast.net [98.234.105.176]) by mx0.deglitch.com (Postfix) with ESMTPSA id A9C238FC27; Tue, 5 Jun 2012 13:04:38 +0400 (MSK) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Stanislav Sedov In-Reply-To: <20120605085202.GI85127@deviant.kiev.zoral.com.ua> Date: Tue, 5 Jun 2012 02:04:33 -0700 Content-Transfer-Encoding: 7bit Message-Id: <07758721-BD54-4732-9B17-83D4CCCF55E0@freebsd.org> References: <4FC96D45.8080904@FreeBSD.org> <20120601193059.af9201da.stas@FreeBSD.org> <4FCD51E4.4030309@FreeBSD.org> <20120605085202.GI85127@deviant.kiev.zoral.com.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.1278) Cc: ports@freebsd.org, Steve Wills , ruby@freebsd.org Subject: Re: Ruby 1.9 as default X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2012 09:04:42 -0000 On Jun 5, 2012, at 1:52 AM, Konstantin Belousov wrote: > On Mon, Jun 04, 2012 at 08:25:08PM -0400, Steve Wills wrote: >> On 06/01/12 22:30, Stanislav Sedov wrote: >>> >>> I'm not sure it's a good idea. >>> Ruby 1.9 still has some nasty bugs on FreeBSD, related to the threads and >>> fork. That is fork in ruby 1.9 hangs sometimes... >> >> The ONLY thing I can find is this: >> >> http://bugs.ruby-lang.org/issues/2097 >> >> 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. Actually, the problem I'm trying to debug right now is more weird. When I run mono via system(3) from the ruby 1.9 process (I mean, exactly system(3), not via some ruby wrapper) twice, it hangs on some umtx the second time. This works all the time. I'm still trying to track it down in mono, though it's not clear how this can happen at all. Isn't execve(2) used by system(3) is supposed to clear everything (mutexes at least)? Thanks! -- ST4096-RIPE