Re: Ruby 1.9 as default

2012-06-05 Thread Konstantin Belousov
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

Re: Ruby 1.9 as default

2012-06-05 Thread Stanislav Sedov
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

Re: Ruby 1.9 as default

2012-06-05 Thread Romain Tartière
On Tue, Jun 05, 2012 at 02:04:33AM -0700, Stanislav Sedov wrote: > 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. T

Re: Ruby 1.9 as default

2012-06-05 Thread Konstantin Belousov
On Tue, Jun 05, 2012 at 02:04:33AM -0700, Stanislav Sedov wrote: > > 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

Re: Ruby 1.9 as default

2012-06-05 Thread Romain Tartière
On Tue, Jun 05, 2012 at 11:42:09AM +0200, Romain Tartière wrote: > I used to see the mono process in the "STOP" state oops: read "pause" state! ^T: > load: 0.07 cmd: mono 46160 [pause] 4854.59r 165.68u 18.57s 0% 169264k ps l 46160: > UID PID PPID CPU PRI NIVSZRSS MWCHAN STAT TT TI

Re: Ruby 1.9 as default

2012-06-05 Thread Steve Wills
> > 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 >>>

Re: Ruby 1.9 as default

2012-06-05 Thread Stanislav Sedov
On Tue, 5 Jun 2012 09:43:55 -0400 "Steve Wills" mentioned: > > > > Is this perhaps the -pthread issue I hit with perl? The issue is that if > you call (dlopen, exec, whatever) a threaded app from a non-threaded on, > it hangs due to the fact that libc takes shortcuts and doesn't initialize > thr

Re: Ruby 1.9 as default

2012-06-05 Thread Stanislav Sedov
On Tue, 5 Jun 2012 11:42:09 +0200 Romain Tartière mentioned: > On Tue, Jun 05, 2012 at 02:04:33AM -0700, Stanislav Sedov wrote: > > 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 vi

Re: Ruby 1.9 as default

2012-06-05 Thread Romain Tartière
On Tue, Jun 05, 2012 at 11:01:12AM -0700, Stanislav Sedov wrote: > Sounds similar. Unfortunately, my app is proprietary. I'll try to > prepare some smaller test case today. Thanks! In the meantime, I am trying to run Banshee with this in /etc/libmap.conf: | [/usr/local/bin/mono] | libthr.so.3

Re: Ruby 1.9 as default

2012-06-05 Thread Stanislav Sedov
On Tue, 5 Jun 2012 20:08:36 +0200 Romain Tartière mentioned: > On Tue, Jun 05, 2012 at 11:01:12AM -0700, Stanislav Sedov wrote: > > Sounds similar. Unfortunately, my app is proprietary. I'll try to > > prepare some smaller test case today. > > Thanks! In the meantime, I am trying to run Bansh

Re: Ruby 1.9 as default

2012-06-05 Thread Romain Tartière
On Tue, Jun 05, 2012 at 11:18:06AM -0700, Stanislav Sedov wrote: > Why do you need this? libpthread.so is exactly libthr right now. meh. I remembered some threading juggling with libpthread / libthr and since ldd reported libthr.so I was wondering if the problem was not back and switching to the

Re: ports/168656: patches for sysutils/rubygem-chef

2012-06-05 Thread swills
Synopsis: patches for sysutils/rubygem-chef Responsible-Changed-From-To: ruby->swills Responsible-Changed-By: swills Responsible-Changed-When: Tue Jun 5 20:02:56 UTC 2012 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=168656

Re: ports/168725: [UPDATE] devel/rubygem-tins: Update to 0.4.3

2012-06-05 Thread sylvio
Synopsis: [UPDATE] devel/rubygem-tins: Update to 0.4.3 Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: sylvio Responsible-Changed-When: Tue Jun 5 21:48:21 UTC 2012 Responsible-Changed-Why: - Pass to team ruby@ http://www.freebsd.org/cgi/query-pr.cgi?pr=168725 __

Re: ports/168727: [PATCH] www/redmine: update and UNBREAK

2012-06-05 Thread sylvio
Synopsis: [PATCH] www/redmine: update and UNBREAK Responsible-Changed-From-To: freebsd-ports-bugs->ruby Responsible-Changed-By: sylvio Responsible-Changed-When: Tue Jun 5 21:51:09 UTC 2012 Responsible-Changed-Why: - Pass to team ruby@ http://www.freebsd.org/cgi/query-pr.cgi?pr=168727 ___

Re: ports/168725: [UPDATE] devel/rubygem-tins: Update to 0.4.3

2012-06-05 Thread swills
Synopsis: [UPDATE] devel/rubygem-tins: Update to 0.4.3 Responsible-Changed-From-To: ruby->swills Responsible-Changed-By: swills Responsible-Changed-When: Wed Jun 6 00:54:53 UTC 2012 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=168725 _

Re: Ruby 1.9 as default

2012-06-05 Thread Steve Wills
On 06/05/12 14:00, Stanislav Sedov wrote: > You usually cannot dlopen the object linked agains pthread from a > non-pthreaded object. Or it is used to be that way. My understanding is that you can now, IFF your non-threaded object is built with -pthread. > Exec should work > fine, I don't see