Re: Loading Eprog in other thread doesn't work

[Sebastian Gniazdowski <psprint@xxxxxxxxxxx>]

On 19.06.2017 at 22:12:53, Bart Schaefer (schaefer@xxxxxxxxxxxxxxxx) wrote:
> Neither signal handling (which includes reaping child processes when
> they exit) nor memory management is thread-safe, and there may be
> shared memory issues with threads and traditional process forking as
> well. The more threads you try to have the more likely you're going
> to be to wander into one of these areas. I'd be very skeptical that
> you can just plop threading into one part of zsh without at least some
> serious semaphore work on the rest of it.

But the only thing that I do concurrently is loading of Eprog. So, open(), read(), that's all. When I invoke execode(), it is the main thread. "source_prepare" does the open, read, while "source_load" takes Eprog that is ready to use.

-- 
Sebastian Gniazdowski
psprint /at/ zdharma.org