On Mon, Aug 23, 2010 at 12:40:48PM +0200, Guido Berhoerster wrote:
> * Jilles Tjoelker <jil...@stack.nl> [2010-08-23 00:32]:
> > If you want to try something, here is a patch. I have verified that the
> > only change to the results of FreeBSD sh's testsuite is that the test
> > builtins/break2.0 starts working (there are still 51 other broken
> > tests). There is no change in output from the posh testsuite (run with
> > -C sh,posix,no-typeset,no-arrays,no-coprocs,no-herestrings,no-history
> > ).
> > diff --git a/src/eval.c b/src/eval.c
> > index d5e5c95..e484bec 100644
> > --- a/src/eval.c
> > +++ b/src/eval.c
> > @@ -307,9 +307,9 @@ setstatus:
> > break;
> > }
> > out:
> > - if ((checkexit & exitstatus) ||
> > - (pendingsigs && dotrap()) ||
> > - (flags & EV_EXIT))
> > + if (pendingsigs)
> > + dotrap();
> > + if ((flags & EV_EXIT) || (checkexit & exitstatus))
> > exraise(EXEXIT);
> > }
> Unfortunately this seems to corrupt variables.
> See the attached test script, after the TERM signal $value
> is not empty anymore but contains garbage.
I think this is the same strange bug as Harald van Dijk reported. The
below gives incorrect output, and quoting the command substitution works
around the issue:
dash -c 'printf "a\t\tb\n" | { IFS=$(printf "\t") read a b c; echo
"|$a|$b|$c|"; }'
In your script, if I write read "$2" instead of read $2 it works.
> Where can I find FreeBSD's sh tests?
You need the tools/regression/bin/sh directory from the head (cvs: HEAD)
branch of the FreeBSD src repository. See
http://www.freebsd.org/developers/cvs.html for access methods. There are
also unofficial git, hg and other mirrors if you prefer that.
The tests are designed to run under perl's prove(1) tool.
The tests test the first instance of "sh" in the PATH. To test other
shells, create a symlink named sh in a new directory and add that
directory in front of your PATH. This is a little clumsy but also
ensures bash and zsh enable their compatibility modes.
--
Jilles Tjoelker
--
To unsubscribe from this list: send the line "unsubscribe dash" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
