From: Andrew Janke <janke@pobox.com>
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
Date: Thu, 12 Mar 2015 01:11:21 -0400 [thread overview]
Message-ID: <55011FF9.1070002@pobox.com> (raw)
In-Reply-To: <91460363.4306421.1426117627753.JavaMail.yahoo@mail.yahoo.com>
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
next prev parent reply other threads:[~2015-03-12 5:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 17:46 John
2015-03-10 10:46 ` Peter Stephenson
2015-03-10 11:16 ` Peter Stephenson
2015-03-10 22:06 ` John
2015-03-11 0:43 ` Bart Schaefer
2015-03-11 9:44 ` Peter Stephenson
2015-03-11 19:55 ` Peter Stephenson
2015-03-11 18:38 ` John
2015-03-11 20:09 ` Peter Stephenson
2015-03-11 23:23 ` John
2015-03-11 23:31 ` Bart Schaefer
2015-03-11 23:47 ` John
2015-03-12 5:11 ` Andrew Janke [this message]
2015-03-12 19:06 ` John
2015-03-12 19:58 ` Peter Stephenson
2015-03-13 4:00 ` Bart Schaefer
2015-03-13 6:44 ` Han Pingtian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55011FF9.1070002@pobox.com \
--to=janke@pobox.com \
--cc=da_audiophile@yahoo.com \
--cc=p.w.stephenson@ntlworld.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).