From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15837 invoked by alias); 11 Mar 2015 00:43:37 -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: 34697 Received: (qmail 22990 invoked from network); 11 Mar 2015 00:43:35 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 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=cXF45zKPgHL7PuR7sJz7eeAiwInrEDsY+jUMwXTMQVg=; b=XMOETUpGIKSQQOoeYhr2/5bfMlEV1dZUaaySHtZ914rSTdGoGg+Vcj4wnHzycmCWCT JjpW6ZS5v667FlOGy2kW4sv4KuDBLKmzhvUPquHvrRLGqBQTpCE9pkmpxKtVqrlVbmu4 SsnOd0wGO3ZvHZQUuJ8NnhGQZq/GUk65UcgHzvLCZaoxydzeqS+pgZ4JVz9KpOI5jg1d rNLgxdZEimHyR8HW4PxFuS40/xHPBCXPj319CGDex8/r/bAAdr5rd3PXrirMoKn6WO+8 nGqljoOQn6/wmYJ0c5xivxxBRMw7WFbxYibGnShOKEZE+4byQn5wgRpRaRgBczOAc06f dTLA== X-Gm-Message-State: ALoCoQmUIalMEp0s3Rf2ffADiftwve3aVLQiYRguC4Cw6Gtm6KPagAk+D8kvYOOU38GdAOKHnmrx X-Received: by 10.202.204.209 with SMTP id c200mr3350274oig.18.1426034611358; Tue, 10 Mar 2015 17:43:31 -0700 (PDT) From: Bart Schaefer Message-Id: <150310174327.ZM13990@torch.brasslantern.com> Date: Tue, 10 Mar 2015 17:43:27 -0700 In-Reply-To: <1396169464.3080953.1426025172139.JavaMail.yahoo@mail.yahoo.com> Comments: In reply to John "Re: Bug: ZSH crashes upon receiving SIGINT" (Mar 10, 10:06pm) References: <20150310104653.181bd618@ntlworld.com> <1396169464.3080953.1426025172139.JavaMail.yahoo@mail.yahoo.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: "zsh-workers@zsh.org" , John Subject: Re: Bug: ZSH crashes upon receiving SIGINT MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 10, 10:06pm, John wrote: } } > we need to know what's going on here. } } I agree with you. Most of the arch-chroot script is over my } head. I have linked it here if the code within is meaningful and } if you have the time to read through it. It is only 309 lines: } http://pastebin.com/yDyuqxqi I took at look at this script. The "unmount" is coming from the exit trap of the bash process that starts the whole thing off. 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.