Date: Tue, 17 May 2005 17:20:31 +0100 (BST) From: Simon Marlow <simonmar@gmail.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/81165: /bin/sh -e bug Message-ID: <200505171620.j4HGKVLK034638@sm.dnsalias.com> Resent-Message-ID: <200505171630.j4HGU1Bc011323@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 81165 >Category: bin >Synopsis: /bin/sh -e bug >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 17 16:30:00 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Simon Marlow >Release: FreeBSD 4.11-STABLE i386 >Organization: >Environment: System: FreeBSD sm.dnsalias.com 4.11-STABLE FreeBSD 4.11-STABLE #43: Sun Jan 23 00:11:26 GMT 2005 simonm@sm.dnsalias.com:/usr/src/sys/compile/RACHEL i386 >Description: There is a bug in ash's handling of the -e flag. See the example below. >How-To-Repeat: $ cat >test.sh if true; then false && true fi echo "test succeeded" $ /bin/sh -e test.sh zsh: 34546 exit 1 /bin/sh -e test.sh $ bash -e test.sh test succeeded Bash works correctly. If the 'if' statement is removed, ash also works correctly. >Fix: unknown. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505171620.j4HGKVLK034638>