X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Tue, 24 Nov 2009 10:25:12 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [1.7] Updated: cygwin-1.7.0-65
Message-ID: <20091124092512.GT29173@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <f4d6f44b0911202003j71954bf0lf5b6696acdfe7e7d AT mail DOT gmail DOT com>  <20091121110204 DOT GB23273 AT calimero DOT vinschen DOT de>  <f4d6f44b0911210743r221b5107qfa4ebee00c9a97e9 AT mail DOT gmail DOT com>  <20091121212239 DOT GD29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911211733t15929d5ctac8e06c977bbc10c AT mail DOT gmail DOT com>  <20091123091612 DOT GE29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911230143k6437ea31n4a7788fdeef8393b AT mail DOT gmail DOT com>  <20091123100122 DOT GI29173 AT calimero DOT vinschen DOT de>  <f4d6f44b0911230607h4d1b76c3x5bc478aecccf7 AT mail DOT gmail DOT com>  <20091123182025 DOT GB11830 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091123182025.GB11830@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Nov 23 13:20, Christopher Faylor wrote:
> On Mon, Nov 23, 2009 at 10:07:05PM +0800, Huang Bambo wrote:
> >There's some diffirence between cygwin and other *nix:
> >In other *nix with this condition, those ended child process could be
> >list by ps command with <defunc>tag, will you fix it?
> 
> Cygwin should produce zombie processes.  You don't see zombie processes
> if the child has exited and the parent goes away though.  In that case
> the process just disappears, just like on linux.
> 
> You *should* see a zombie when the parent is alive by not waiting for
> children.

Hmm, but you don't.  Huang's example code forks a child and the parent
returns to the select loop without reaping the child via wait.  When the
child exits after its 3 second sleep, the handle to the child process
does not get closed, and the cygpid shared memory regions for the child
pid still exists.  But the process list does not show the child process
at all.  Nor will you find it in /proc.

That's not a regression, though.  The same occurs in 1.5.25.  However,
I have a vagure memory that we really saw zombies in the process list
way back when.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple