Zsh Mailing List Archive
Messages sorted by:
Re: Builtin + process substitution can't be interrupted
- X-seq: zsh-workers 40866
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Builtin + process substitution can't be interrupted
- Date: Sat, 18 Mar 2017 21:15:38 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=xolhmitXz6s4PGW5ufiVTAT1xCdEhFRBnxmsDnf9AIw=; b=lbhoLLSaMDzAq8S9zOLchUQze6Gqz/nHSWvypXg4gASY0R9QYV2Njh4vKbjRnL5atd DSSDVKR71Hya+ZYZqF5k+whSx5i3U1fo2X8Rx6k6ElwGL5UEf9pAelPiYSTCkfni0EW/ NJN6q/h4UJlpR6dubIVy29JyPgi/61iY+6GHkXzY44/6yBa/iOIS3VxNqaRpDcK7Zvdi EqcAen4aIylXbYfWBVd7zJVbvziZ/9NdeWaLhlsmYRspxlQJ7Ej+I0fRKjmWP6UEAkIi Zt2DOLm/ijZYwfyyA/y/69lfXbeZyQWbLGg9MGet8JtY578lpi4qtO7bfC8YqinUUpkE h+qQ==
- In-reply-to: <170314082528.ZM26126@torch.brasslantern.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <170314082528.ZM26126@torch.brasslantern.com>
On Mar 14, 8:25am, Bart Schaefer wrote:
} Subject: Builtin + process substitution can't be interrupted
} Try for example
} % : >(sleep 10)
} Enters zwaitjob() to wait for SIGCHLD and despite dont_queue_signals() the
} INT signal is blocked, as also are QUIT and TSTP.
Update on this -- examination with a debugger indicates that although
INT is blocked, QUIT and TSTP are received. However, they don't call
any handler and sigsuspend() just goes back to waiting for CHLD.
The INT signal is then received and processed after the child has
exited, so it's being held rather than ignored.
My current guess at what's happening is that the parent shell treats
the process substitution as part of the foreground job, and expects
that it will receive the signal and choose whether or not to exit.
However, the process substitution is not actually in the TTY process
group (it puts itself in its own group, I checked with strace), so
it never receives any signals from the keyboard.
I'm not sure where to go from there.
Messages sorted by: