--- Comment #12 from tromey at gcc dot gnu dot org 2005-11-08 21:01 ---
Fix checked in.
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
Status|A
--- Comment #11 from tromey at gcc dot gnu dot org 2005-11-08 21:00 ---
Subject: Bug 23763
Author: tromey
Date: Tue Nov 8 21:00:15 2005
New Revision: 106655
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106655
Log:
PR libgcj/23763. From [EMAIL PROTECTED]
* jav
--- Comment #10 from tromey at gcc dot gnu dot org 2005-11-08 20:59 ---
Subject: Bug 23763
Author: tromey
Date: Tue Nov 8 20:59:20 2005
New Revision: 106654
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106654
Log:
PR libgcj/23763. From [EMAIL PROTECTED]
* jav
--- Comment #9 from tromey at gcc dot gnu dot org 2005-11-08 19:44 ---
I'm handling this.
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo
--- Comment #8 from aeby at graeff dot com 2005-10-26 18:04 ---
no problem ...
I thought, resetting the signal handler to SIG_DFL before unblocking might be a
good idea in the (not very probable) case a SIGCHLD signal is either in the
signal queue or is otherwise received between sigpro
--- Comment #7 from tromey at gcc dot gnu dot org 2005-10-26 09:01 ---
Sorry for the delay on this.
The patch looks reasonable enough to me. It needs a small
amount of reformatting and a ChangeLog entry.
Also I think the call to signal() is not needed, a custom
handler is reset to the d
--- Comment #6 from aeby at graeff dot com 2005-10-26 08:48 ---
I have just tested against 4.0.2 and the bug is still there (no surprise, of
course).
--
aeby at graeff dot com changed:
What|Removed |Added
---
--- Additional Comments From aeby at graeff dot com 2005-09-15 14:27
---
Created an attachment (id=9734)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9734&action=view)
workaround: patch against GCC 4.0.1 unblocking SIGCHLD before execvp()
--
http://gcc.gnu.org/bugzilla/show_b
--- Additional Comments From aeby at graeff dot com 2005-09-15 14:24
---
I don't think this bug is linked with 23758. No matter if you call unsafe
procedures before or after fork() SIGCHLD ist still blocked at the point where
execvp() is called. It seems the posix-threads code does expli
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-10
02:20 ---
This is might be the same problem as described in PR 23758.
--
What|Removed |Added
OtherBugsD
--
What|Removed |Added
Known to fail||4.0.0 4.0.1
Known to work||3.3.3
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
--- Additional Comments From aeby at graeff dot com 2005-09-07 13:18
---
Created an attachment (id=9687)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9687&action=view)
Sample program that hangs when executed via Runtime.exec()
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23
--- Additional Comments From aeby at graeff dot com 2005-09-07 13:17
---
Created an attachment (id=9686)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=9686&action=view)
Execs "exectest" and demonstrates how it hangs
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23763
13 matches
Mail list logo
