X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=peT7Bn+e7HwZBauYVSrA3jQ1ZasE
	4UfeKUyzLGPLMFAVdf/jbF0GorYKdlZF0JGbZAY4PlbFxuJ6YrJoko18LCBj6nh5
	vWWMCjHoF3osNv8oZFE94J6cXb7qmhMVqUOWdFSGr9o9ML+6Rtf+CGvAhJwLTFa6
	stoce2Nm1vr0Ca8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=w5S0+s5FaMBxj+S6yqdCcwEaDds=; b=xK
	w69VoAhrb6sofL0J+6K67V1mmNb/0hrnlEFyyotTj9pP2f8OGUKvbbXQvTj1iC4g
	eqzKBweGaQnjywlDIXxsv5gad+BIB6ou/CMBmkXnMZjrz1hSWXsK49zZoeXblcYc
	u1bG3YkK1UEKUgut+fAugFds3Xv+6y+e2M96ZtiNE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: etr-usa.com
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: ps questions
From: Warren Young <warren AT etr-usa DOT com>
In-Reply-To: <20141218185114.GJ10824@calimero.vinschen.de>
Date: Thu, 18 Dec 2014 11:54:26 -0700
Message-Id: <90541515-EA98-4E9C-B6F2-8C0642BFCEDA@etr-usa.com>
References: <CAO2ddnZChb-n9+Z1YEWCFSA=WTaYfkmHdjMZk7Te5JYckUDE+Q AT mail DOT gmail DOT com> <5492EDFC DOT 5080608 AT gmail DOT com> <CAO2ddnZHs=4GxUJtjgoyTXO2Or3oKzY6Rck=m9Mqfj6DgWUQUg AT mail DOT gmail DOT com> <20141218171116 DOT GF10824 AT calimero DOT vinschen DOT de> <8F8B22BA-B007-4F10-9B4F-9BD963D17059 AT etr-usa DOT com> <20141218173346 DOT GH10824 AT calimero DOT vinschen DOT de> <71891584-9B1C-430D-9A15-8EC385EB3F3F AT etr-usa DOT com> <20141218185114 DOT GJ10824 AT calimero DOT vinschen DOT de>
To: cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id sBIIshkk022576

On Dec 18, 2014, at 11:51 AM, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:

> On Dec 18 11:40, Warren Young wrote:
>> On Dec 18, 2014, at 10:33 AM, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
>> 
>>> On Dec 18 10:26, Warren Young wrote:
>>>> 
>>>> ...Cygwin doesn’t do something similar?
>>> 
>>> Cygwin isn't a kernel and the process
>>> information is kept in shared memory regions held by the parent process
>>> and the process itself.  This model has limitations you don't have on a
>>> real kernel.
>> 
>> I’m aware of that, but can’t the DLL see both the birth and death of
>> every Cygwin process?  Birth via either DllMain() or execvp(2), and
>> death via one of the methods here:
> 
> Aren't we talking about fetching info from non-Cygwin processes?

Of course.  But if you keep a table of all Cygwin processes, you can tell whether you’re being asked for info for a native process vs a Cygwin one, and handle <defunct> differently for the two cases.
--
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