Re: [Rubycocoa-talk] RBCocoaInstallRubyThreadSchedulerHooks: couldn't find autoreleasePool

[Laurent S. <lsa...@ap...>]

If you're seeing this message when running on 10.5 a RubyCocoa app  
that embeds a RubyCocoa framework built in 10.4, then it's expected.

The threading support for 10.4 is not compatible with the support in  
10.5, and vice-versa.

Currently the 2 different code paths are separated during compilation,  
but we could select them at runtime instead, which would allow the  
same RubyCocoa framework built for 10.4 to run on both 10.4 and 10.5.

Laurent

On Nov 30, 2007, at 2:44 PM, Benjamin Jackson wrote:

> Hi all,
>
> We are embedding RubyCococa and the patched libruby with  
> standaloneify, and it works out of the box on 95% of the machines,  
> but some of our users have been getting crashes due to problems with  
> ruby threads:
>
> "RBCocoaInstallRubyThreadSchedulerHooks: couldn't find  
> autoreleasePool ivar"
>
> Also seeing a warning about ruby threads not being able to be used  
> without patches to the ruby interpreter.
>
> Can anyone suggest what might be going on here, and if there might  
> be something specific to the users' setup which is FUBAR-ing  
> RubyCocoa? I'm certain that I'm linking against my own version of  
> libruby, as the same program works on Tiger machines out of the box  
> with no changes to the installed ruby.
>
> Thanks in advance,
>
> Ben
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4_______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk