Re: [Chicken-users] calling CHICKEN_eval from different threads

[Jan Baumgart]

Sorry, I've mixed up the terminology for reentrant.
I actually meant the opposite:
The chicken runtime system gets called only after the previous call 
(from another thread) has returned.
Chicken_eval gets blocked by a mutex lock.

I've also tested the scenario without the locks, to avoid any 
possibility of deadlocks, while
making sure, the threads don't call chicken at the same time. But 
chicken_eval still hangs.

felix winkelmann wrote:
> On Thu, Feb 26, 2009 at 3:19 AM, Jan Baumgart <address@hidden> wrote:
> > Hi!
> >
> > Is it possible, to make subsequent calls to CHICKEN_eval from within
> > different nonreentrant(!) threads?
>
> No, the chicken runtime system is not thread-safe.
>
>
> cheers,
> felix