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=HVFYqe7hTjxRbtoLkPfu0PKSSeEnX1NBmj5EzHD2Xe4ONMKUUsh73
	L4l72au6aAfpkI8t0Fr0UpMDNqNExATFGTfLgL+265pBS2wk6Hlav/z5pXiLqLZk
	eb36pxa3iN5aIp/PHydmfRGmMw26ZvXk67xdTkhLgCEafueMLf8qUs=
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=TzXjmmlFPCLSFcIp6GoCmVF/Qjc=; b=JB7CtWZMMVIq0w/p2TKENLItNMna
	uNvqK814BPsWcXATgpjuNWvGVuw88CJUuoQ01tn4ePz1Ix1wzaa/zywtg5Q7AnUz
	8W5kTp1DXktt9sjI5DSHt8TcIrX/13+mM58zF2Atsujij4pFmp5uEZAH3yY7bJGG
	6sl33j96anP2BIQ=
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.9 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=me, me!, Hx-languages-length:1541, day
X-HELO: mout.kundenserver.de
Date: Wed, 27 Feb 2019 17:38:58 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: Ken Brown <kbrown AT cornell DOT edu>
Cc: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: Fork issue with timerfd
Message-ID: <20190227163858.GE4133@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: Ken Brown <kbrown AT cornell DOT edu>,	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
References: <133d62b5-afd5-ae73-b950-7b50471e111e AT cornell DOT edu> <3142aff3-c7c3-187f-233e-089c5dc15ea2 AT cornell DOT edu> <20190225100300 DOT GH4133 AT calimero DOT vinschen DOT de> <20190225202050 DOT GP4133 AT calimero DOT vinschen DOT de> <e2cae181-b96a-2ce0-34b8-f8a48714c828 AT cornell DOT edu> <20190226085730 DOT GQ4133 AT calimero DOT vinschen DOT de> <20190226094838 DOT GS4133 AT calimero DOT vinschen DOT de> <d367bf35-3c62-15e9-f292-ff709066ec4c AT cornell DOT edu> <20190227161904 DOT GC4133 AT calimero DOT vinschen DOT de> <79567e26-1232-f462-9867-a463da0be56f AT cornell DOT edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="Uw+RRa3pmtkgiNaD"
Content-Disposition: inline
In-Reply-To: <79567e26-1232-f462-9867-a463da0be56f@cornell.edu>
User-Agent: Mutt/1.11.3 (2019-02-01)

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

On Feb 27 16:31, Ken Brown wrote:
> On 2/27/2019 11:19 AM, Corinna Vinschen wrote:
> > On Feb 26 13:39, Ken Brown wrote:
> >> On 2/26/2019 4:48 AM, Corinna Vinschen wrote:
> >>> On Feb 26 09:57, Corinna Vinschen wrote:
> >>>> On Feb 26 00:01, Ken Brown wrote:
> >>>>> I did get the following, however, during one of the trials (while e=
macs was idle):
> >>>>>
> >>>>> 1 [main] emacs 246 C:\Users\kbrown\src\emacs\i686-emacs26\src\emacs=
.exe: ***
> >>>>> fatal error - CreateThread failed for pipesel - 0x0<0x0>, Win32 err=
or 8
> >>>>
> >>>> It's hard to imagine how this is related.  CreateThread fails due to
> >>>> memory problems?!?  A timerfd does not use a lot of resources, just a
> >>>> 96 bytes struct on the cygheap, a single page shared memory region, =
and
> >>>                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^'
> >>>
> >>> This was at least the intention, but I accidentally created a 64K
> >>> region.  Fixed in git and new snapshort forthcoming.
> >>
> >> Looks good so far.  I've been running emacs on x86 for about an hour, =
running
> >> lots of subprocesses, with no problems.  I'll keep using it throughout=
 the day.
> >=20
> > Ken?  Any news?  If you're satisfied with the current state, I'd like
> > to push 3.0.2 out.
>=20
> I've been using emacs extensively on both x86 and x86_64 with the latest=
=20
> snapshot, and I've had no further problems.  I think 3.0.2 is ready to go.

You don't know how relieved I am to read that.

Thanks for testing and pulling this through with me!


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--Uw+RRa3pmtkgiNaD
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlx2vSEACgkQ9TYGna5E
T6D22w/8Cq8OrC0tIjIV4g23rC+mJ+2yzpDBbO15AhzmOlc37QoWfDDSLap6qQ8m
Rj3f3jVMvtfaOBSRn0uT/hy7jHGEu/O34oS3O+X23GclLi9GMKpxPBTTfp0RHvum
EgdPKhPWOtEWhk4N5dT0YAt3h9T4+konsthdooUfqG/T3/6C2z8uHofO9lvSCGAP
EBOANN8dF4fpJZ1wSrQX9+YqmQ//T/Uc3O9opzgcZRf7eD8V7jchjjyE4pSG2hb+
PjGRYgLYfrtV3/TcMwIpVMwX4V5ylkG/LBMaDw+rvGDYl/3JsPQ+QioSXRhCLPb0
YNDn2Exl3FD/yeiXpZfA1ONHpR5LUu7lIuCz42zLrMTChG0BMotNMfy9JzqNKuuL
58ZuHQwbGr1+Y1QIPgtQ/qDjvyljN3y2dCXMoWgdw+po9JnJKuhyBT//NDYrVJa/
bBtn6FXAzKT44bIo+RfVT9MsXwl3lQHTRP9xXDl+R2MJ69WHQf+kJKD3vTfK+GJJ
sxbsl74ZP70M8pG2yCShsUKkOautr9USLv/yhUp5HCv45f/dhLW95AEInrGfTMGv
JB4JhYwcmziOoYIDMnJ8AZFJ6jc/Uq0PAD7YPU2Q0ltn3rpWE/N3yCUxHCgxFFix
N831I1VeKbyF3XOBDSLnEWXlunsUaAXB0HDx62eIcOrKTcN8C3M=
=cMQf
-----END PGP SIGNATURE-----

--Uw+RRa3pmtkgiNaD--