From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35977-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 10650 invoked by alias); 3 Aug 2015 20:58:25 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 35977
Received: (qmail 25645 invoked from network); 3 Aug 2015 20:58:23 -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.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no
	version=3.4.0
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:message-id:date:in-reply-to:comments
         :references:to:subject:mime-version:content-type;
        bh=EPi2ctV81nfNJ3DgNu0IvLp6CsaYldRNZKGZfnjL90o=;
        b=YoImExbVepaQ62OsghW+X6EPBw9FygrtA7hR8Dfiy15y5VCXCUMqcz3ZhdWr70N992
         tCcIlEywUz47d2Q2BZWqGCCUbyIEpAd34LWlw0o6woHUvg4i5m3/2xlbm9oaMFLipWAC
         6DyQGSGfuXgFyHPO/cHgHEYX64IhMRCPQK0qgSspV8fTuiQciMCxJLtGF6TUMmOp5TCj
         3s5HDh4UC0hTBJ6zsYjlpIlpwOnaCDgq0n1rXXQwwTNZzgDj0LAa7FBF4ZRlsXuXXt5H
         Vl34FneJGwdQH2DfKRNHNjdfqkAKNNH/G980kXAWuN82pWaGKU/PQwefidazW2pz/eXV
         Kp/w==
X-Gm-Message-State: ALoCoQk0EIyNBGccBQMjz3VloRwPsTPtMtLX0ljvrQGvd+tJYmNwqu3ukpUMTsZwCA3dku6cqV7d
X-Received: by 10.182.114.234 with SMTP id jj10mr38449obb.70.1438635501684;
        Mon, 03 Aug 2015 13:58:21 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <150803135818.ZM24977@torch.brasslantern.com>
Date: Mon, 3 Aug 2015 13:58:18 -0700
In-Reply-To: <CA+=GgY5iZfgUag_V1jqmCv4=PUGBmaV2cNWTDjSO4DAZ+zm-iQ@mail.gmail.com>
Comments: In reply to Mathias Fredriksson <mafredri@gmail.com>
        "Re: Deadlock when receiving kill-signal from child process" (Aug  3, 11:36pm)
References: <CA+=GgY7mHkyK4NJQ6m7y-HpVPKOuKx3-bkJqRHriKzZ662_iwA@mail.gmail.com> 
	<150803085228.ZM24837@torch.brasslantern.com> 
	<CA+=GgY5iZfgUag_V1jqmCv4=PUGBmaV2cNWTDjSO4DAZ+zm-iQ@mail.gmail.com>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: Deadlock when receiving kill-signal from child process
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Aug 3, 11:36pm, Mathias Fredriksson wrote:
}
} 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 you can get a stack trace from the deadlocked zsh, that would be
helpful.

A stack trace from the SIGILL's zsh might also be helpful, but that is
less likely.