From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34705-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 2030 invoked by alias); 12 Mar 2015 05:23:14 -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: 34705
Received: (qmail 13900 invoked from network); 12 Mar 2015 05:23:02 -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,DKIM_SIGNED,
	DKIM_VALID,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	messagingengine.com; h=x-sasl-enc:message-id:date:from
	:mime-version:to:cc:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=smtpout; bh=Ji23egET2bYF3yKjIrobhx
	x9ixo=; b=DR9l6uOi8nh4EwSb+3Yx/8ayMXghuQ6yjd+UClr2jjD1pxK3UoydeQ
	em3A/mAwzOKX7f27GoNGhdZ2zvMTQq6J1XZUVCmrJtA55qo0s+vTd4Vo9u8XPmxm
	v1QyVa5Y26mtjjR2YSmlZHHF/dLfdQ5Z5qBN3e12D+joC92tThlPk=
X-Sasl-enc: VXV4kV/MTg95g1w7FJxcOvk/te9v0GXS9TuYRnY8qFi9 1426137084
Message-ID: <55011FF9.1070002@pobox.com>
Date: Thu, 12 Mar 2015 01:11:21 -0400
From: Andrew Janke <janke@pobox.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: John <da_audiophile@yahoo.com>, 
 Bart Schaefer <schaefer@brasslantern.com>
CC: Peter Stephenson <p.w.stephenson@ntlworld.com>, 
 Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug: ZSH crashes upon receiving SIGINT
References: <CAH+w=7YxUWi4GQ3zCvArLm8bidvRa3YgDkmO4VJWimUWASJkHg@mail.gmail.com> <91460363.4306421.1426117627753.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <91460363.4306421.1426117627753.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi folks,

I was able to set up an Arch Linux instance that can consistently 
reproduce this issue. It's on a public-facing server, so if having 
access to work with this directly would help you debug it, send me a 
direct email with a desired username and public SSH key and I'll set you 
up with an account.


To set up a server to reproduce the issue:
Start with a fresh Arch Linux installation, and then:

pacman -Syy
pacman -S zsh arch-install-scripts
mkdir -p /chroots/mini
pacstrap -d -i /chroots/mini base zsh

Then to make the breakage happen:

arch-chroot /chroots/mini /bin/zsh

Wait for the prompt and hit Ctrl-C. It'll immediately produce those 
umount and input error messages.

After you get errors from this, your mount table will be in an unclean 
state and subsequent arch-chroot calls will fail. To clean up manually 
so you can arch-chroot again:

umount /chroots/mini/dev/pts
umount /chroots/mini/dev


Cheers,
Andrew

On 3/11/15 7:47 PM, John wrote:
>> Actually Peter wants you to run the zmodload and print from here inside the chroot, not from outside it.
>
> <<Headsmack>>
>
> Running it from within the chroot gives the opposite output.  I googled for how I can toggle this parameter but didn't find a good answer.  Please advise.
>
> # zmodload zsh/parameter
> # print $options[MONITOR]
> off