From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21705 invoked by alias); 11 Mar 2015 09:45:48 -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: 34698 Received: (qmail 19435 invoked from network); 11 Mar 2015 09:45:33 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 X-AuditID: cbfec7f4-b7f126d000001e9a-8f-55000e25185e Date: Wed, 11 Mar 2015 09:44:47 +0000 From: Peter Stephenson To: Bart Schaefer , "zsh-workers@zsh.org" Cc: John Subject: Re: Bug: ZSH crashes upon receiving SIGINT Message-id: <20150311094447.765e7489@pwslap01u.europe.root.pri> In-reply-to: <150310174327.ZM13990@torch.brasslantern.com> References: <20150310104653.181bd618@ntlworld.com> <1396169464.3080953.1426025172139.JavaMail.yahoo@mail.yahoo.com> <150310174327.ZM13990@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsVy+t/xK7qqfAyhBo/OGVo8fniVyWL/9Ics FgebHzI5MHvcXzWF1WPWrMNMHqsOfmAKYI7isklJzcksSy3St0vgyjg77xdbwTHOiu8n/zA3 MF5j72Lk5JAQMJHYtfgrC4QtJnHh3nq2LkYuDiGBpYwSBx51M0I4PUwS1+bdZYZwtjFKXPq3 BqydRUBV4uPd2WA2m4ChxNRNsxlBbBGBGIl5s06ygtjMAkoSG5ougdUICxhLHDv6lA3E5hWw l+j52wcW5xSwkrh6cAcr3OrWlyDbODn4BfQlrv79xARxn73EzCtnGCGaBSV+TL7HArFAS2Lz tiaoZfISm9e8BesVElCXuHF3N/sERuFZSFpmIWmZhaRlASPzKkbR1NLkguKk9FxDveLE3OLS vHS95PzcTYyQwP+yg3HxMatDjAIcjEo8vDej/4UIsSaWFVfmHmKU4GBWEuEtOfk/RIg3JbGy KrUoP76oNCe1+BAjEwenVANjxG7eN48XNp/rDTQKefV27iqHu3tN226vCNW+5bVr+1SvbdUb QnuFpjdPu7Hu847k1wsfsyR/P5Op/XDD11W/snd69O3aI7/Xqv8pZ4r1drlZb38n3760+0fk ppoy9WWvdLZEqBy+4XXAXOoL8+uXV3Jlp79+8XGn0se/iVOm/efW+cXe7et+XlKJpTgj0VCL uag4EQDFhkcTWgIAAA== On Tue, 10 Mar 2015 17:43:27 -0700 Bart Schaefer wrote: > So I *think* what's happening is: > > Bash starts "unshare" which becomes the TTY process group leader. > > Unshare starts zsh which does not make itself the process group leader > (see previous -workers list discussions of zsh executing inside PID > namespaces, of which "unshare" creates one). > > The ^C therefore is delivered to "unshare" which exits, ending the > bash script and executing the trap, which removes the tty device. > > This causes zsh to get I/O error and exit. > > It's *possible* that this is already "fixed" in development versions > of zsh, though most of the PID namespace changes had to do with avoiding > being process group leader rather than forcibily becoming so. It's also > not clear that this is actually zsh's problem; it seems to me that the > arch-chroot script and/or "unshare" are not doing things they should be. The PID namespace issue I remember is from the docker thread, zsh-workers/34503. http://www.zsh.org/mla/workers/2015/msg00427.html I only remember the problem with unreaped children in that case, but I'll refresh my mind when I get home. pws