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:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=cWUvW2bNYg4lkSaQNybD8U1guukW6S5XLayyYk5Au7P9pw017bixt
	MwJUesCPEAzpoTEt+UiQCRoGGRNx/1QYYAJDVgxfo+jSB4vL3R+brLr8x/GfnOY7
	rKOakf8+rlG1xwKqIjqZ3mWfbNT5thc740n6yVwelHI8swOOWoQ3BY=
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:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=5mqAf2eYRENn5F8YAFi+uStEu9E=; b=ONAy5WP39jNulABVjECpDP5f0usZ
	5PbAp3TCXD+ZAMMKpGL2FkhDjn9wJikuzW5+jVAnQkYHB9Q1JHZZ0WT44em6a0lo
	gvmpX3oGGrIFcE3BdNAjZrtVNaJ1whyOe31bT2xKGRkRz8TxvAXGvXL1hQevZnNZ
	ief1GMMuwEl92PM=
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-Spam-SWARE-Status:	No, score=-100.4 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=informed
X-HELO:	mout.kundenserver.de
Date:	Fri, 8 Feb 2019 15:48:27 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	Michael Haubenwallner <michael DOT haubenwallner AT ssi-schaefer DOT com>
Cc:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.7
Message-ID:	<20190208144827.GR13951@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	Michael Haubenwallner <michael DOT haubenwallner AT ssi-schaefer DOT com>, cygwin AT cygwin DOT com
References:	<20190207182735 DOT GG13951 AT calimero DOT vinschen DOT de> <8a2f041f-f8f7-6e17-5d97-5a168440009b AT ssi-schaefer DOT com> <20190208113158 DOT GH13951 AT calimero DOT vinschen DOT de> <17e339bb-2115-bf22-7291-04215aab3150 AT ssi-schaefer DOT com> <20190208122126 DOT GM13951 AT calimero DOT vinschen DOT de> <20190208122338 DOT GN13951 AT calimero DOT vinschen DOT de> <b07e6ba2-0ce0-4662-7a02-bda6ce3b0108 AT ssi-schaefer DOT com> <20190208130635 DOT GO13951 AT calimero DOT vinschen DOT de> <20190208132807 DOT GP13951 AT calimero DOT vinschen DOT de> <6b182191-b235-fcbb-5b25-66243950043c AT ssi-schaefer DOT com>
MIME-Version:	1.0
In-Reply-To:	<6b182191-b235-fcbb-5b25-66243950043c@ssi-schaefer.com>
User-Agent:	Mutt/1.10.1 (2018-07-13)

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

On Feb  8 15:43, Michael Haubenwallner wrote:
>=20
>=20
> On 2/8/19 2:28 PM, Corinna Vinschen wrote:
> > On Feb  8 14:06, Corinna Vinschen wrote:
> >> On Feb  8 13:52, Michael Haubenwallner wrote:
> >>> On 2/8/19 1:23 PM, Corinna Vinschen wrote:
> >>>> On Feb  8 13:21, Corinna Vinschen wrote:
> >>>>> On Feb  8 12:51, Michael Haubenwallner wrote:
> >>>>>>
> >>>>>> For now it seems like there's an inconsistency with PIDs:
> >>>>>> A first process PID 100, receives PID 101 from spawn(),
> >>>>>> but in the new process getpid() returns 102:
> >>>>>>
> >>>>>> $ ./dospawn /bin/bash -c 'echo $$'
> >>>>>> 12625
> >>>>>> waitpid: pid 12624 status 0x0
> >>>>>
> >>>>> Oh, hmm.  If you call spawnve, rather than execve, a new child pid
> >>>>> is generated in spawnve, rather than just keeping the callers pid.
> >>>>>
> >>>>> However, apparently the child invents its own pid in pinfo::thisproc
> >>>>> after being spawned.  But actually this should only occur for forked
> >>>>> processes aore processes started from non-Cygwin parents.
> >>>>
> >>>> Does that help, by any chance:
> >>>> [nope]
> >>>
> >>> How should the child be informed at all about the new cygpid value ge=
nerated in
> >>> parent's child_info_spawn::worker() ?
> >>
> >> I just realized this myself.  The old method creating Cygwin pids just
> >> fetched the pid from GetCurrentProcessId(), which was right for spawned
> >> (but not execed) processes.  For the new pid we might have to give this
> >> to the child via child_info_spawn.
> >=20
> > This works for me, can you test this, too, please?
>=20
> Looks good to me as well, I'm going to start my hours running use case no=
w.

Sounds good, thanks.  I'll push this change now.  We can always
rework it if it's insufficient.

> > I pushed your forkable branch to master, btw.  Would you mind to do the
> > honors in the ;rease notes at cygwin/release/3.0 and doc/new-features.x=
ml?
>=20
> Ok, just preparing the tests first. Thanks a lot!

No worries, as long as I know you're here to answer questions ;)


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--HLsZ5Z1opAQvdr2J
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxdlrsACgkQ9TYGna5E
T6Bk1RAApL0PuUExqU+IaQlKe6zZAi8MgNc4Iab2W2JxFMst/UBlILuvL6+n1iDC
TSAbjYSp8VhkT9n2AdrtLiRTvRtKvGlBTm1OCctGoBC5geO4ogMoia1309ShYQmA
b25jHByK32H1ie3NbG1+0zzbIxojrrESz82L8xogI//jHRog9msn17THdqdoef5o
U4sb023HZApcSidoBcar4EGJH9mzgbdjGbFFHqOXl4N1dRNQIHS4jROnUsTGNrej
TNZnzSACRfRNbiDZOpcTNBGXEPkxVrH/GXNk2z5v158pBufBaG/OJSuxCFEhjwJO
JzAxuvwYWSMqQEaQIs09XFOyJJse751CCl+pOBdAaHe1LRhObPzCiRGat8GO4I0C
toEBRBPujsuK4mcsUgdsq5PDqOhMsDHwclcwgs+iZ1hSiiwFfDUy7QLIufKVqAHK
O6bRX8OJzbudZ/WU9M2ECB39ofmtFC13s7GkqzBFit35G0NvUYIPeH2g/Q8e0s65
fprrMwlf64mv2/WR7ozp8RKIEYSpB6ySWeMCC4aXg+2Sea2cTlxntV3oQ60k4ll+
AbfEESmL355GFmVMWCiRmhJh8NzTwiWnB5KV09/C6U7/GDwWNjXQiSVLBzAGpyG5
V4WUOOfNiFzHJ/UeL6s5/KbCYxWr6/FaeDNMDtVJqOwGf++RHnQ=
=Cwkn
-----END PGP SIGNATURE-----

--HLsZ5Z1opAQvdr2J--

- Raw text -