public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cyberflex at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/33218] Process.waiFor() Process.destroy() misbehave for childs which are not reacting to Ctrl+C SIGQUIT
Date: Thu, 30 Aug 2007 09:34:00 -0000	[thread overview]
Message-ID: <20070830093405.12786.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33218-14857@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2007-08-30  9:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 14:56 [Bug java/33218] New: " cyberflex at mail dot ru
2007-08-28 15:59 ` [Bug java/33218] " daney at gcc dot gnu dot org
2007-08-28 16:43 ` cyberflex at mail dot ru
2007-08-28 16:56 ` daney at gcc dot gnu dot org
2007-08-29  6:19 ` daney at gcc dot gnu dot org
2007-08-29  6:19 ` daney at gcc dot gnu dot org
2007-08-29 10:17 ` cyberflex at mail dot ru
2007-08-30  9:34 ` cyberflex at mail dot ru [this message]
2007-08-30  9:35 ` cyberflex at mail dot ru
2007-08-30  9:36 ` cyberflex at mail dot ru
2007-08-30  9:37 ` cyberflex at mail dot ru
2007-08-30  9:41 ` cyberflex at mail dot ru
2007-08-30 17:44 ` daney at gcc dot gnu dot org
2007-08-31  9:43 ` cyberflex at mail dot ru
2009-01-02 12:21 ` laurent at guerby dot net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070830093405.12786.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).