Date: Tue, 17 May 2005 20:00:28 GMT From: Parv <parv@pair.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/81165: /bin/sh -e bug Message-ID: <200505172000.j4HK0Stu042657@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/81165; it has been noted by GNATS. From: Parv <parv@pair.com> To: Simon Marlow <simonmar@gmail.com> Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: bin/81165: /bin/sh -e bug Date: Tue, 17 May 2005 15:53:07 -0400 in message <200505171620.j4HGKVLK034638@sm.dnsalias.com>, wrote Simon Marlow thusly... > > 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. Just a data point ... "test succeeded" is printed by /bin/sh of FreeBSD 5.3-p13, ksh93 20050202, & bash 3.0.16_1. - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505172000.j4HK0Stu042657>