delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/04/29/19:28:08

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <4272C2F7.9030905@agilent.com>
Date: Fri, 29 Apr 2005 16:27:51 -0700
From: Earl Chew <earl_chew AT agilent DOT com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Help understanding process tree
References: <4270F2F5 DOT 5010000 AT agilent DOT com>
X-OriginalArrivalTime: 29 Apr 2005 23:27:54.0042 (UTC) FILETIME=[1154E1A0:01C54D13]

Earl Chew wrote:
> I'd like help understanding why Process Explorer shows cygwin
> child processes as orphans, but win32 child processes as children.
> 
> How is this so?

I think I've discovered the reason for this is that during
the fork/exec, the child that does the exec is discarded and
replaced with a new process that executes the new application.

Earl


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019