This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT
- From: "daney at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 28 Aug 2007 16:56:21 -0000
- Subject: [Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT
- References: <bug-33218-14857@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from daney at gcc dot gnu dot org 2007-08-28 16:56 -------
Looking at the current code, it seems that we may have a problem if we
destroy() a process that has already exited. The kill(2) man page suggests
that ESRCH could result, in which case we would throw an InternalError. Must
investigate...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218