-
Bug
-
Resolution: Duplicate
-
P3
-
None
-
1.0.2, 1.1.5
-
generic, x86
-
generic, windows_95, windows_nt
java.lang.Runtime.exec(String[]command, String[] env) says that it will
execute the command with the given environment. This implies that if the
environment array is empty, the command should be executed with the
empty environment. This does not happen; in this case it is executed with
the environment inherited from the parent process. However, that effect
can be achieved by passing "null" for the environment array, as compared to
an empty array.
Currently, there is no way to execute a command with an empty environment.
Accidentally inheriting the environment of the parent process can lead to
some very strange side effects for JavaTest and JCK.
The bug exists in JDK1.0.2, through to at least 1.1.3.
execute the command with the given environment. This implies that if the
environment array is empty, the command should be executed with the
empty environment. This does not happen; in this case it is executed with
the environment inherited from the parent process. However, that effect
can be achieved by passing "null" for the environment array, as compared to
an empty array.
Currently, there is no way to execute a command with an empty environment.
Accidentally inheriting the environment of the parent process can lead to
some very strange side effects for JavaTest and JCK.
The bug exists in JDK1.0.2, through to at least 1.1.3.
- duplicates
-
JDK-4115037 win32 exec does not properly set up environment. Causes failure in exec'd progs
-
- Closed
-
-
JDK-4109888 (process spec) Semantics of external process is not defined in JLS
-
- Closed
-