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 24175
From: Peter Stephenson <pws@xxxxxxx>
To: Guillaume Chazarain <guichaz@xxxxxxxx>, "Zsh Hackers' List" <zsh-workers@xxxxxxxxxx>
Subject: Re: deadlock caused by gettext usage in a signal handler
Date: Fri, 7 Dec 2007 10:35:33 +0000
In-reply-to: <20071207000207.2eb7e5e7@xxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
Organization: CSR
References: <20071130203534.1d1ea29c@xxxxxxxx> <20071204203017.35a29727.p.w.stephenson@xxxxxxxxxxxx> <20071207000207.2eb7e5e7@xxxxxxxx>

On Fri, 7 Dec 2007 00:02:07 +0100
Guillaume Chazarain <guichaz@xxxxxxxx> wrote:
> It appears that glibc's fork is playing with locks:
>
> This patch solved the problem for me:

Thanks for looking at that.  The traditional zsh way is to queue signals
around an operation, but fork() is atomic to the calling code and blocking
should be quicker, so your patch is fine and I've committed it.

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070

Follow-Ups:
- Re: deadlock caused by gettext usage in a signal handler
  - From: Guillaume Chazarain

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

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