Re: [Rubycocoa-talk] Re: Newbie: stack level too deep??

[Frank I. <ill...@ma...>]

Jonathan,

thanks for the information. The Sydney project sounds interesting.  
How would I proceed to get to a Cocoa app that may call methods ruby  
classes (via RubyCocoa) from different threads?
Is it straight forward to start with Syndey?

Cheers

  Frank


On 28.11.2005, at 10:53, Jonathan Paisley wrote:

> On 28 Nov 2005, at 7:21, Frank Illenberger wrote:
>
>> I could dig a little deeper and found the following stack trace is  
>> repsonsible for a "Stack level too deep" exception:
>
> Ah, the problem is that the ruby code is being executed on a  
> secondary NSThread. Unfortunately, Ruby is not thread-safe with  
> respect to OS-level threads (which an NSThread is).
>
> Ruby checks from time to time that the stack has not overflowed,  
> and since the non-main thread will have a different area of memory  
> for its stack than the main thread, Ruby thinks a stack overflow  
> has occurred.
>
> I'm afraid that there's probably no good way to work around this at  
> the moment. It may be possible to get RubyCocoa running with Sydney  
> [1], which apparently gives OS-level thread support. Do let us know  
> if you give that a shot.
>
> Sorry I don't have better news for you
> Cheers
> Jonathan
>
>
> [1] http://blog.fallingsnow.net/articles?page=2
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Rubycocoa-talk mailing list
> Rub...@li...
> https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk