X-Recipient: archive-cygwin@delorie.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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; q=dns; s=default; b=VgjV
	S+ZoWOpbB5VEDSe0cTBxFctAOvLsmWhuR+JUTWk6VruwZIanQ07pMbjKYuGZUNQI
	cLI5XSgq90dST8GRSyxedgaIc53XYwuzte5dci1AEprtjvf6MOyFIWfsnd9bvuNW
	C5uvRVXISalxKmweKMSUUU+Psk8Pdy5ueTGwnHM=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type; s=default; bh=30SSsMVua1
	Pre43hGlfDTUFc2Yc=; b=Smyl4RB16DWjgjHr/Fj47tbPIi+99VRezQ+nLOTK15
	BRiS9YYI9H85Vccet33jrrrjAaFsABYeD2G4RVzbYTJJwthQOljLoejmtx+QqkxN
	WblysOxCP5Cn/RyAETAew1xqefZ0ZaNVoHLILOfFXTq5sZqLbCAaXa2GVtKpPkXD
	M=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2
X-HELO: mx1.redhat.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.1.0-0.1
To: cygwin@cygwin.com, Ben Woodard <woodard@redhat.com>
References: <558706D5.1020508@cornell.edu> <20150622110835.GE28301@calimero.vinschen.de> <20150626111249.GS31223@calimero.vinschen.de> <558D3F4C.6090207@cornell.edu> <20150626141437.GV31223@calimero.vinschen.de> <558D62D7.8010709@cornell.edu> <20150626153647.GX31223@calimero.vinschen.de> <558D8409.2000400@cornell.edu> <20150626200512.GA30636@calimero.vinschen.de> <558DD1F3.4010301@cornell.edu> <20150627145259.GB23036@calimero.vinschen.de>
From: Eric Blake <eblake@redhat.com>
Openpgp: url=http://people.redhat.com/eblake/eblake.gpg
X-Enigmail-Draft-Status: N1110
Message-ID: <55A58ACF.5010206@redhat.com>
Date: Tue, 14 Jul 2015 16:18:55 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <20150627145259.GB23036@calimero.vinschen.de>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="95oa6ddqnMMG3SMTXC19PfSjl4iw7A4U6"
X-IsSubscribed: yes

--95oa6ddqnMMG3SMTXC19PfSjl4iw7A4U6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 06/27/2015 08:52 AM, Corinna Vinschen wrote:
> The problem is probably that there are still resources in use which
> didn't get free'd.  I'll check next week if I can do anything about it.
> Ideally with a simple testcase than emacs :}

Is libsigsegv an appropriate testcase?  There are several other
applications that then optionally use libsigsegv for stack overflow
protection (such as m4 and awk), as well as for user-managed page
faulting for garbage collection purposes (such as guile).  In fact, I'm
a bit surprised that emacs rolls its own protection instead of taking
advantage of libsigsegv - it might be worth suggesting that to upstream
emacs.

Upstream libsigsegv comes with a fairly decent testsuite for low-level
testing of what types of SIGSEGV handling is possible (regardless of
whether that recovery was done by native windows hacks as in the current
build, or via sigaltstack which is what I hope will happen when it is
reconfigured against the new cygwin).  And if those tests aren't enough
it is also a fairly simple test case using (32-bit) m4 (when linked
against a rebuilt libsigsegv) to do:

 echo 'define(a,a(a))a' | m4

--=20
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


--95oa6ddqnMMG3SMTXC19PfSjl4iw7A4U6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Public key at http://people.redhat.com/eblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJVpYrPAAoJEKeha0olJ0NqaB0H/RP5Tfmn2loe4pOa76Tpa7zT
Q0HidwNTXg3ndY31ZE+EEBF0WDLs3L3uoCGaoFV2BHE3FUGbe3TEnO/a5EstFypt
INmDqO1TWDI5i53TzeJUENQJwspAQuVKzQROWtuhzqoJirjTBTpdCXTwhqoxTZSX
51gMABtAi09LPE7iwke6z++uHO5cRwv/WSZRpqSDD6hMbJLDetQr22kVI59+SiLA
ZFexCudL32Sm8ceka9HNKmf7+jPqpIOH1XFdaMltauSOuOytsHxXng9q8FvkI8CT
q/iHOZsrrSHaFrmHCJcepPFe0QWexVU58fIox0aZEzyRzz8RZD/fpvBijSm6l6k=
=ijHv
-----END PGP SIGNATURE-----

--95oa6ddqnMMG3SMTXC19PfSjl4iw7A4U6--
