Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: deadlock caused by gettext usage in a signal handler

X-seq: zsh-workers 24177
From: Guillaume Chazarain <guichaz@xxxxxxxx>
To: "Zsh Hackers' List" <zsh-workers@xxxxxxxxxx>
Subject: Re: deadlock caused by gettext usage in a signal handler
Date: Fri, 7 Dec 2007 11:46:31 +0100
In-reply-to: <20071207103533.47776664@news01>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20071130203534.1d1ea29c@xxxxxxxx> <20071204203017.35a29727.p.w.stephenson@xxxxxxxxxxxx> <20071207000207.2eb7e5e7@xxxxxxxx> <20071207103533.47776664@news01>

Le Fri, 7 Dec 2007 10:35:33 +0000,
Peter Stephenson <pws@xxxxxxx> a écrit :

> The traditional zsh way is to queue signals
> around an operation

Oh, I didn't know queue_signals().

> but fork() is atomic to the calling code and blocking
> should be quicker

Ok, but I don't mind changing it to queue_signals().

> so your patch is fine and I've committed it.

Thanks, how about reverting the strerror_r one (also in zsh-4.2)?

-- 
Guillaume

Follow-Ups:
- Re: deadlock caused by gettext usage in a signal handler
  - From: Peter Stephenson
- Re: deadlock caused by gettext usage in a signal handler
  - From: Bart Schaefer

References:
- deadlock caused by gettext usage in a signal handler
  - From: Guillaume Chazarain
- Re: deadlock caused by gettext usage in a signal handler
  - From: Peter Stephenson
- Re: deadlock caused by gettext usage in a signal handler
  - From: Guillaume Chazarain
- Re: deadlock caused by gettext usage in a signal handler
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author