Bug 18447

This problem is on /bin/sh.

If /bin/sh evaluates a string with `eval' statement and the string
has semicolon at the end, then /bin/sh doesn't process the `eval'
statement.

for example:

  $ /bin/sh -c 'eval echo t'
  t
  $ /bin/sh -c 'eval echo t;'
  $

or

  $ cat test.sh
  #! /bin/sh
  cmd1='eval echo 1;'
  cmd2='eval echo 2'
  eval $cmd1
  eval $cmd2
  $ /bin/sh test.sh
  2
  $

And if the string has multiplue eval statement, then /bin/sh doesn't
process first eval statements, but processes others.

for example:

  $ /bin/sh -c 'eval echo 1; eval echo 2; eval echo 3;'
  2
  3
  $

I think its behavior is /bin/sh's bug.  Other shells reading Bourne
shell script, such as bash or SunOS's /bin/sh, process all eval
statement for above cases.  But NetBSD's /bin/sh is same as FreeBSD.

Fix: To fix, apply this patch to src/bin/sh/parser.c
How-To-Repeat: 
Simple example is

 $ /bin/sh -c 'eval echo 1; eval echo 2;'

The result is

 2

but we expected 

 1
 2