Re: Bug: ZSH crashes upon receiving SIGINT

[Peter Stephenson <p.stephenson@samsung.com>]

On Tue, 10 Mar 2015 17:43:27 -0700
Bart Schaefer <schaefer@brasslantern.com> 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