[Bug libgcj/23758] java::lang::ConcreteProcess::nativeSpawn unsafe

2007-04-09 Thread daney at gcc dot gnu dot org
--- Comment #4 from daney at gcc dot gnu dot org 2007-04-09 18:49 --- Fixed on the trunk. -- daney at gcc dot gnu dot org changed: What|Removed |Added Status|

[Bug libgcj/23758] java::lang::ConcreteProcess::nativeSpawn unsafe

2007-04-09 Thread daney at gcc dot gnu dot org
--- Comment #3 from daney at gcc dot gnu dot org 2007-04-09 18:40 --- Subject: Bug 23758 Author: daney Date: Mon Apr 9 18:40:20 2007 New Revision: 123676 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=123676 Log: PR libgcj/23758 * java/lang/natPosixProcess.cc (n

[Bug libgcj/23758] java::lang::ConcreteProcess::nativeSpawn unsafe

2007-04-06 Thread daney at gcc dot gnu dot org
-- daney at gcc dot gnu dot org changed: What|Removed |Added AssignedTo|unassigned at gcc dot gnu |daney at gcc dot gnu dot org |dot org

[Bug libgcj/23758] java::lang::ConcreteProcess::nativeSpawn unsafe

2005-11-08 Thread daney at gcc dot gnu dot org
--- Comment #2 from daney at gcc dot gnu dot org 2005-11-08 21:20 --- Could someone elaborate? If the child is killed, it is dead and it did not matter anyhow. The child is not going to be getting random async signals. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23758

[Bug libgcj/23758] java::lang::ConcreteProcess::nativeSpawn unsafe

2005-09-06 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-07 00:49 --- Confirmed based on: http://www.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_04.html -- What|Removed |Added