public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Fort <david.fort@irisa.fr>
To: linux-kernel@vger.kernel.org
Subject: Unkillable Zombie process under 2.6.3 and 2.6.4
Date: Thu, 11 Mar 2004 17:01:41 +0100	[thread overview]
Message-ID: <40508D65.9000601@irisa.fr> (raw)

Hi list,
i have some troubles with some totally unkillable zombie process:
Here's how i can get unkillable zombies debug multi-threaded program 
using gdb and
in the execution my program popens a command, sometimes i get the 
following gdb message

waiting for new child: No child processes.
(gdb)

And gdb give me back the prompt. I have the impression that the child 
process has
been effectively launched.
If i ask gdb to continue the process goes on but the incriminated thread 
looks freezed. When
in this state i can contact other threads, but gdb is stuck(Ctrl+C 
doesn't work).

Killing -9 my program doesn't have any effect. But killing -9 gdb 
effectivelly kills gdb
but not my program(which is a son of gdb). Shouldn't the kernel finish 
the job with zombie
process when their father die ?(there's nobody to catch signals, or 
return codes).

My big problem is that the faulty program keeps its binding sockets 
opened, so i can't
launch anything on that ports.

-- 
Fort David, Projet IDsA
IRISA-INRIA, Campus de Beaulieu, 35042 Rennes cedex, France
Tél: +33 (0) 2 99 84 71 33



             reply	other threads:[~2004-03-11 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 16:01 David Fort [this message]
     [not found] ` <20040311151729.57e3d936.akpm@osdl.org>
2004-03-12 13:54   ` Unkillable Zombie process under 2.6.3 and 2.6.4 David Fort
2004-03-12 14:06     ` Christian Borntraeger
2004-03-12 14:30       ` David Fort
     [not found]       ` <4051C8C5.5090204@irisa.fr>
2004-03-12 16:37         ` David Fort

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=40508D65.9000601@irisa.fr \
    --to=david.fort@irisa.fr \
    --cc=linux-kernel@vger.kernel.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