[Bug libgcj/29324] add wait handling hook

2007-05-12 Thread daney at gcc dot gnu dot org
--- Comment #7 from daney at gcc dot gnu dot org 2007-05-12 19:52 --- I think the patch solves the problem. -- daney at gcc dot gnu dot org changed: What|Removed |Added

[Bug libgcj/29324] add wait handling hook

2007-05-12 Thread daney at gcc dot gnu dot org
--- Comment #6 from daney at gcc dot gnu dot org 2007-05-12 18:38 --- Subject: Bug 29324 Author: daney Date: Sat May 12 17:37:55 2007 New Revision: 124638 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124638 Log: PR libgcj/29324 * include/posix-threads.h (_Jv_Bl

[Bug libgcj/29324] add wait handling hook

2006-10-05 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/29324] add wait handling hook

2006-10-05 Thread daney at gcc dot gnu dot org
--- Comment #5 from daney at gcc dot gnu dot org 2006-10-05 17:02 --- Another idea: In the SIGCHLD signal handler record the pid of the process that exited. Then look it up in the pidToProcess map. If it belongs to the libgcj runtime, then do waitpid(pid, ...) on it. Otherwise ignore

[Bug libgcj/29324] add wait handling hook

2006-10-04 Thread pinskia at physics dot uc dot edu
--- Comment #4 from pinskia at physics dot uc dot edu 2006-10-05 05:48 --- Subject: Re: add wait handling hook On Thu, 2006-10-05 at 05:42 +, daney at gcc dot gnu dot org wrote: > > --- Comment #3 from daney at gcc dot gnu dot org 2006-10-05 05:42 --- > One way to fix it

Re: [Bug libgcj/29324] add wait handling hook

2006-10-04 Thread Andrew Pinski
On Thu, 2006-10-05 at 05:42 +, daney at gcc dot gnu dot org wrote: > > --- Comment #3 from daney at gcc dot gnu dot org 2006-10-05 05:42 --- > One way to fix it would be to have a reaper thread for *each* Process. Then > the reaper could do a waitpid(pid...) instead of waitpid(-1...)

[Bug libgcj/29324] add wait handling hook

2006-10-04 Thread daney at gcc dot gnu dot org
--- Comment #3 from daney at gcc dot gnu dot org 2006-10-05 05:42 --- One way to fix it would be to have a reaper thread for *each* Process. Then the reaper could do a waitpid(pid...) instead of waitpid(-1...). If one only spawns a few processes, this would be fine. This would allow u

[Bug libgcj/29324] add wait handling hook

2006-10-02 Thread tromey at gcc dot gnu dot org
--- Comment #2 from tromey at gcc dot gnu dot org 2006-10-02 18:39 --- Yes, it really is a bug. libgcj can reap a child process started by some other library. This means it is hard to use libgcj in conjunction with other libraries which may want to do their own subprocess bookkeeping.

[Bug libgcj/29324] add wait handling hook

2006-10-02 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-10-02 18:35 --- Hmnm, is this really a bug, waitpid is used only in the reaper thread. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29324