From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23886 invoked by alias); 3 Aug 2015 20:37:04 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 35976 Received: (qmail 17057 invoked from network); 3 Aug 2015 20:37:02 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=1ZSjeJWjHaP6q/Wm209nOeo9hSkMTsQfIbQCXErl1GY=; b=kjl5IRFUgQ9IAhPVHn4ZKUIzxkjF2ZHrb9PNVC1ALSGfgm6NqVhj6xegHHj88V9rGf y/9EQmQ0pWzy/3l4DFB0S8Dp6KOAk/HIrTqF0FE03tPBZYGYdvJIEbxR+JwsitwXghE2 HCuL6WeMz7c4dFaSnhswFpM+idExSd6XU43gy5Lz+6uUS4hIrWB0zu0uz58JRQYu/M9b RgINquJNtQiEBvxJObReXlBnZ1pLVMFONub5jKMxC3Er+pGZXqyXGnSODn9GiLO9sjmn xv5ER7eIVVNg6itHfSLItBQi/cs2+IvdShzj93/1pSucDaaFOKT9FNMbM1qHtD4pobkw mGsg== X-Received: by 10.60.178.99 with SMTP id cx3mr18692656oec.50.1438634219165; Mon, 03 Aug 2015 13:36:59 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <150803085228.ZM24837@torch.brasslantern.com> References: <150803085228.ZM24837@torch.brasslantern.com> From: Mathias Fredriksson Date: Mon, 3 Aug 2015 23:36:19 +0300 Message-ID: Subject: Re: Deadlock when receiving kill-signal from child process To: zsh-workers@zsh.org Content-Type: text/plain; charset=UTF-8 On Mon, Aug 3, 2015 at 6:52 PM, Bart Schaefer wrote: } } Is that 5.0.8 or 5.0.8-dev-1 from SourceForge git? It is 5.0.8 } } I *think* this problem should have been fixed by workers/35642 (git } 811027a22a806f753537abee1575da8714d3fa0a) and I cannot reproduce with } ZSH_PATCHLEVEL = zsh-5.0.8-154-gd90f921. I just tried applying this patch to 5.0.8 and I am still able to reproduce, occasionally zsh even exits with the following (maybe related): zsh: illegal hardware instruction ./zsh_deadlock.zsh If workers/35642 alone was supposed to fix this I think it remains unfixed.