From: David Fort <david.fort@irisa.fr>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unkillable Zombie process under 2.6.3 and 2.6.4
Date: Fri, 12 Mar 2004 14:54:46 +0100 [thread overview]
Message-ID: <4051C126.5080902@irisa.fr> (raw)
In-Reply-To: <20040311151729.57e3d936.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
Andrew Morton wrote:
>Would you have time to prepare a little test app to demonstrate this?
>
>Thanks.
>
>
>
I've wrote this little app that do nothing complicated: it just launch a
thread that do popen in its body.
This programs sticks gdb completly, i don't know who is to blame gdb or
the kernel.
The fact is that there's something really strange here.
I'm trying to build a test app that can trigger the case where GDBed
process become unkillable zombies
(i have some still running on my box).
I've explored several ideas i had:
-related to TLS -> playing around with the tlsData var didn't show
anything
-SIGCHLD intercepted by the program and not caught by gdb -> even
without the signal handler i get the
bug
I'm gonna modify the app to test that the apps doesn't become unkillable
when it has a socket in WAIT_STATE.
Attached is a tarbal that contains: the program, the makefile and a
quite long report of the behaviour that i'm
seeing while debugging and my .config.
gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)
glibc-2.3.3-10mdk
2.6.4 kernel
--
Fort David, Projet IDsA
IRISA-INRIA, Campus de Beaulieu, 35042 Rennes cedex, France
Tél: +33 (0) 2 99 84 71 33
[-- Attachment #2: kbug1.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 9899 bytes --]
next prev parent reply other threads:[~2004-03-12 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 16:01 Unkillable Zombie process under 2.6.3 and 2.6.4 David Fort
[not found] ` <20040311151729.57e3d936.akpm@osdl.org>
2004-03-12 13:54 ` David Fort [this message]
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=4051C126.5080902@irisa.fr \
--to=david.fort@irisa.fr \
--cc=akpm@osdl.org \
--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