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: "cyberflex at mail dot ru" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 30 Aug 2007 09:34:05 -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 #7 from cyberflex at mail dot ru 2007-08-30 09:34 -------
Problem is reproducible, but it likely should be posted to other list.
It looks that behaviour of particular utility "rfcomm" is such specific that
it not only ignores some signals but also forks one more child in detached
state.
Here how I do reproduce it:
As root do
1. attach my USB bluetooth dondle and bring it up "hciconfig hci0 up"
2. run "./test"
3. run "ps ax | grep rfcomm"
Very soon I see that the only instance of rfcomm is running (PID is not
changed) and instances of rfcomm started later are exiting because interface
hci0 is busy.
Some processes still need SIGINT due to notify their children before exiting or
be killed with other signal such as -9
The bug, posted here looks like needs resolution as INVALID.
Oh, I terribly sorry
What do you think?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33218