X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 24 Nov 2009 10:35:01 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [1.7] Updated: cygwin-1.7.0-65 Message-ID: <20091124153500.GA31706@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20091121110204 DOT GB23273 AT calimero DOT vinschen DOT de> <20091121212239 DOT GD29173 AT calimero DOT vinschen DOT de> <20091123091612 DOT GE29173 AT calimero DOT vinschen DOT de> <20091123100122 DOT GI29173 AT calimero DOT vinschen DOT de> <20091123182025 DOT GB11830 AT ednor DOT casa DOT cgf DOT cx> <20091124092512 DOT GT29173 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091124092512.GT29173@calimero.vinschen.de> 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: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Tue, Nov 24, 2009 at 10:25:12AM +0100, Corinna Vinschen wrote: >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 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. Ok, I suspected as much. I just wanted to squash the notion that this wasn't possible in Windows. It may be broken now but it is possible. cgf -- 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