fix open_port with many unset env vars

The erlang:open_port spawn and spawn_executable directives can include
    an {env, Env} directive to set up environment variables for the
    spawned process. Variables can be unset with {"NameOfVariable",false}.
    A bug in ert/emulator/sys/unix/sys.c could cause unset variables
    to not be unset. This would typically happen if there where more
    variables to be unset than there where already set variables in the
    destination evironment.

    Fix this problem for unix and add a new regression test for it to
    the port test suite. Windows does not seem to have the same problem.

0 files changed, 0 insertions, 0 deletions