zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Value of $? after signal
Date: Tue, 11 Sep 2001 14:36:26 +0000	[thread overview]
Message-ID: <1010911143626.ZM24553@candle.brasslantern.com> (raw)
In-Reply-To: <200109101450.KAA75715@raptor.research.att.com>

On Sep 10, 10:50am, David Korn wrote:
}
[Bart wrote:]
} > [I just sent a very similar message to the zsh-workers list.]
} > 
} >        The  return  value of a simple command is its exit status,
} >        or 128+n if the command is terminated by signal n.
} > 
} > What does ksh do?
} 
} First of all, ksh uses
} 	256+signo
} for processes that terminate due to a signal.  Otherwise, there
} is no way to distinguish between a process that does exit(130)
} and one that terminated due to a SIGINT.

I was looking at this a bit more.  There are a couple of places in exec.c
and jobs.c where zsh tests (the equivalent of) `lastval & 0200' to decide
whether a child process got a signal.  That means a child that explicitly
calls exit(130) can fool zsh into interrupting a loop (jobs.c:338) or (I
think) "propagating" a signal to the entire process group (exec.c:1070).

To see the jobs.c problem, compare:

    yes | for x in a b c; do echo $x; (exit 2); echo $?; done

    yes | for x in a b c; do echo $x; (exit 130); echo $?; done

I haven't come up with an example for the exec.c issue, but it should be
something similar to the above (requires a loop on the right of a pipe).

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


       reply	other threads:[~2001-09-11 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200109101450.KAA75715@raptor.research.att.com>
2001-09-11 14:36 ` Bart Schaefer [this message]
2001-09-08  6:50 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=1010911143626.ZM24553@candle.brasslantern.com \
    --to=schaefer@brasslantern.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).