From: Jonathan P. <jp...@dc...> - 2005-11-28 09:53:58
|
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 |