From: Dan Nelson <dnelson@allantgroup.com>
To: zsh-workers@sunsite.dk
Subject: Re: [4.2/4.3] Bug with wait and trapped signals
Date: Fri, 17 Feb 2006 12:08:10 -0600 [thread overview]
Message-ID: <20060217180810.GD52817@dan.emsphone.com> (raw)
In-Reply-To: <20060217142816.GE1708@prunille.vinc17.org>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
In the last episode (Feb 17), Vincent Lefevre said:
> zsh (all versions?) does not interrupt a "wait" when it receives a
> signal for which a trap has been set.
>
> For instance, consider the following script:
>
> #!/usr/bin/env zsh
> echo "PID = $$"
> sleep 60 &
> trap 'echo term; exit 0' TERM
> wait
Here's the test I've been using. All shells I've tested except zsh and
FreeBSD's ash interrupt the wait, but only bash returns the correct
value from wait #1. I tested Solaris 10 /bin/sh and /bin/ksh, FreeBSD
5's /bin/sh, zsh-4.2.6 and ksh93-20060124 ports, and Debian's
bash-2.05b-14 and ash-0.5.2-5.
--
Dan Nelson
dnelson@allantgroup.com
[-- Attachment #2: waittest --]
[-- Type: text/plain, Size: 779 bytes --]
#! /bin/sh
#
SIG=15
echo "\
Correct order is:
parent waiting on \$childpid
child sending signal to \$parentpid
parent received signal
wait #1 finished, gotsig=1, status=a number > 128, possibly $(($SIG+128))
child exiting
wait #2 finished, gotsig=0, status=33
"
gotsig=0
signal_handler() {
echo "parent received signal"
gotsig=1
}
child() {
sleep 2
echo "child sending signal to pid $parentpid"
kill -$SIG $parentpid
sleep 2
echo "child exiting"
exit 33
}
parentpid=$$
echo "parent's pid is $parentpid"
child &
childpid=$!
trap signal_handler $SIG
echo "parent waiting on pid $childpid"
wait $childpid
cstatus=$?
echo "wait #1 finished, gotsig=$gotsig, status=$cstatus"
gotsig=0
wait $childpid
cstatus=$?
echo "wait #2 finished, gotsig=$gotsig, status=$cstatus"
next prev parent reply other threads:[~2006-02-17 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 14:28 Vincent Lefevre
2006-02-17 18:08 ` Dan Nelson [this message]
2006-02-18 0:50 ` Vincent Lefevre
2006-02-18 17:31 ` Peter Stephenson
2006-02-18 17:36 ` Peter Stephenson
2006-02-21 4:06 ` Bart Schaefer
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=20060217180810.GD52817@dan.emsphone.com \
--to=dnelson@allantgroup.com \
--cc=zsh-workers@sunsite.dk \
/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).