bin/134881: sh(1) with 'set -e' exits immediately in tested eval command

Mikolaj Golub at
Sat May 23 20:50:02 UTC 2009

>Number:         134881
>Category:       bin
>Synopsis:       sh(1) with 'set -e' exits immediately in tested eval command
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 23 20:50:01 UTC 2009
>Originator:     Mikolaj Golub
>Release:        current
FreeBSD fbsd.zhuzha.ua1 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r191131M: Sat May  9 10:48:19 EEST 2009     root at zhuzha.ua1:/home/golub/freebsd/build/obj/home/golub/freebsd/src/sys/NOSWAPPING  i386

FreeBSD zhuzha.ua1 7.2-PRERELEASE FreeBSD 7.2-PRERELEASE #8: Sun Apr 26 12:08:58 EEST 2009     root at zhuzha.ua1:/usr/obj/usr/src/sys/DEBUG  i386

FreeBSD kopusha.onet 6.4-STABLE FreeBSD 6.4-STABLE #0: Tue May  5 03:04:10 EEST 2009     root at kopusha.onet:/usr/obj/usr/src/sys/GENERIC  i386
Aleksey Cheusov posted the following sctipt to, which shows bug in sh(1):


    set -e

    if eval false; then
        echo 'Really?'

    echo "Your shell is good"




More information about the freebsd-bugs mailing list