zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <psprint@zdharma.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Loading Eprog in other thread doesn't work
Date: Tue, 20 Jun 2017 04:42:57 +0200	[thread overview]
Message-ID: <etPan.59488bb1.127d0173.63ea@zdharma.org> (raw)
In-Reply-To: <etPan.59483072.5b1b299a.63ea@AirmailxGenerated.am>

On 19.06.2017 at 22:12:53, Bart Schaefer (schaefer@brasslantern.com) 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


  parent reply	other threads:[~2017-06-20  2:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 14:37 Sebastian Gniazdowski
2017-06-19 20:12 ` Bart Schaefer
2017-06-20  4:37   ` Sebastian Gniazdowski
2017-06-20  6:02     ` Bart Schaefer
     [not found] ` <etPan.59483072.5b1b299a.63ea@AirmailxGenerated.am>
2017-06-20  2:42   ` Sebastian Gniazdowski [this message]
2017-06-20  5:59     ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=etPan.59488bb1.127d0173.63ea@zdharma.org \
    --to=psprint@zdharma.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).