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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=uY+aCsvSGZUO6WEtregOAps6HyFyVXdc9esunMXu629CotbBo1DlI
	3C/P9MYMadi5AnyADBgHyUtDsZifc2V46VvLW30D4cUYIgHkK442ZgxXH6yrqay4
	z6G7Dx8LqPb1JhLgJkmrvVRcAUtl5Ry3Ugr8iVicqf6Bsuw7dGXA0M=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=fRXEroDTH6pZYRL8+wV6+kOf5DY=; b=edXgYIAdf8ESNBQnDP4AnYXXWdUV
	PYv3Senz091lccDNuOHEYGcldVGmK8Hds38PP3YUT4f4i5QoRGUBYj1lXueYDYNR
	Nh4o0kgIhnKqmiMhytIrOwUzHrlOHvmZwB8Kd90DIQftvM+Mgc084Ur5+BWdHhvh
	p/oGTzCITXlW3+s=
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=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Thu, 18 Dec 2014 20:10:01 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: ps questions
Message-ID:	<20141218191001.GL10824@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT 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> <90541515-EA98-4E9C-B6F2-8C0642BFCEDA AT etr-usa DOT com>
MIME-Version:	1.0
In-Reply-To:	<90541515-EA98-4E9C-B6F2-8C0642BFCEDA@etr-usa.com>
User-Agent:	Mutt/1.5.23 (2014-03-12)

--DvpQYQy10PodzGf7
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Dec 18 11:54, Warren Young wrote:
> On Dec 18, 2014, at 11:51 AM, Corinna Vinschen <corinna-cygwin AT cygwin DOT com=
> wrote:
>=20
> > On Dec 18 11:40, Warren Young wrote:
> >> On Dec 18, 2014, at 10:33 AM, Corinna Vinschen <corinna-cygwin AT cygwin.=
com> wrote:
> >>=20
> >>> On Dec 18 10:26, Warren Young wrote:
> >>>>=20
> >>>> ...Cygwin doesn=E2=80=99t do something similar?
> >>>=20
> >>> Cygwin isn't a kernel and the process
> >>> information is kept in shared memory regions held by the parent proce=
ss
> >>> and the process itself.  This model has limitations you don't have on=
 a
> >>> real kernel.
> >>=20
> >> I=E2=80=99m aware of that, but can=E2=80=99t the DLL see both the birt=
h and death of
> >> every Cygwin process?  Birth via either DllMain() or execvp(2), and
> >> death via one of the methods here:
> >=20
> > Aren't we talking about fetching info from non-Cygwin processes?
>=20
> Of course.  But if you keep a table of all Cygwin processes, you can
> tell whether you=E2=80=99re being asked for info for a native process vs a
> Cygwin one, and handle <defunct> differently for the two cases.

That may be possible, but it's just not implemented.  Under the hood,
the process your seeing in /proc is not really the native Windows
process, but rather a Cygwin process stub.  The stub has a process info
shared mem region, but it's essentially defunct, the only task it's
handling is to wait for the non-Cygwin process to exit.  It may be
possible to add functionality to the stub process, but given that the
actually running process is a non-Cygwin process, it will be fairly
limited.  And, seriously, there was just no reason to put that much
work into bookkeeping for native processes.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--DvpQYQy10PodzGf7
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUkyaJAAoJEPU2Bp2uRE+gP50P/i6dbm3Ve4m/IU8KM7nMweIs
Y6yotOSAbGgqzPEA3+QC9Z+i8808l4PT3PIpGqnatu5XdtWnUnQP7uEFs/Rmmpwv
m+h5K1EmU8HcDVydJlAydv7WgipJClbn1fuNae45l0UE+tz82T5fAa4aVJmTM280
ZSItNeTjNauF10Gw9X7OF67n02ovWy6rUW/1HLBEpDk/CNsVIjujQITiPID5GnAJ
bOY6QcBnqlGSZWt1bkvgYu01VmeGJMNhPzjZmClDkkb4upSx0yyZa9Y1yD8LWDqC
Ef269FdDDEdZrvpOHMfFAmQH6t/fZfshMH6fd2C4SdEha1M9xpy3QBYQ/rWvUGfb
/kzVW5eRw2QaMwtYwomUAdKn//9BRZ+hvnBUPljosNusxDEvR1SiTn+dLra2otrh
7lYqmJgZMwGbYDIU4EHbh1LvFmG9Idyx5s2gLR0E1QuarfyAaOGoOEVP4iteSApw
ER4KO9kf4kGcVXlo4aZLMHjLYSVMlkqvwheGNQW77Mn8IihvOLX3kaLzTA6kMaFS
8rfztByYRGnHUbl18ytk3PFLmNsbtUX4Hmeivzp73Skocv4eYML18TkdODwxdD6D
U5FatzLn7yhCRiy3HqH7S+r1ojdXK3wp2R+5bd7jDBmEBo7o9C9qVlO8kigjtpl9
tyyY7N7c+OFTzkdV1xbj
=60YK
-----END PGP SIGNATURE-----

--DvpQYQy10PodzGf7--

- Raw text -