From: Chuck Remes <cremes.devlist@...>
Date: 2010-09-28T06:13:23+09:00
Subject: Re: interpreter cannot enter in the context from another thread.


On Sep 27, 2010, at 3:55 PM, Ralph Shnelvar wrote:

> Luis,
> 
> 
> 
> Monday, September 27, 2010, 2:45:09 PM, you wrote:
> 
> LL> On Sep 27, 5:30 pm, Ralph Shnelvar <ral...@dos32.com> wrote:
>>> [Note:  parts of this message were removed to make it a legal post.]
> 
>>> This is a continuation of the thread:
>>>  Re: Segmentation Fault; more info?
> 
>>> Luis Lavena said:
> 
>>> "Please note that Ruby 1.8.x is not multithread and that the
>>> interpreter cannot enter in the context from another thread."
> 
>>> Could use please explain this further?
> 
>>> Unless I am missing something, 1.8.7 implements green threads ... at least according to Dave Thomas (pg. 171 in *Programming Ruby 1.9*)
> 
> LL> Yes, but you're using FXRuby which is a C component.
> 
> LL> Since you haven't provided a sample code that shows the segmentation
> LL> fault. I must tackle all the possible issues, including the spawn of
> LL> threads by FXRuby and using Ruby-based callbacks.
> 
> LL> So, Ruby green threads are OK, as long you don't mix them with real
> LL> threads. In your post you mention "4 different threads"
> 
> LL> We are just guessing all due your lack of code.
> 
> LL> --
> LL> Luis Lavena
> 
> Could you please explain what you mean by "interpreter cannot enter in the context from another thread."

A native thread (e.g. one created by the FXRuby C extension) cannot call back into the ruby runtime context to execute more ruby code without causing lots of pain.

You should show us some code.

cr