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=iOkwjF812Nq4JT+5WEOAFm3Q7JAl1BL6ZEY8CDJ1669l1+rjSEs14
	KAJLQSbqf285Wi512ZRE9P3cAKZDS2ktvZ/wMgkjpg6CvQzFCCHhXwCC6/qeaRFO
	URk5Iu8sEC729T2fpQnnNCXPptWCmpF3AjTgdSMVi0ROL0JUcb5BeY=
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=5gYnO9/XlbfnrKK8su370bIp9Vg=; b=UrZHLumd9PkueoKRgNEMGh0Qr3pG
	6Nz0V8zjUc4ERVp+/tET0YDaqrgd1BbdX9P9hSg0fA80pUYQxqMkaeu0QwLGdGo2
	2noWqIRHkMXcbOOC8Elxo/wdV7twjAO3UxeKC7UnB+/j8Zli5zQ+/fAt8GQoq2GG
	KNmltG+7u19F7pw=
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=-4.5 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Thu, 2 Jul 2015 14:20:47 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.1.0-0.1
Message-ID: <20150702122047.GS2918@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20150626200512 DOT GA30636 AT calimero DOT vinschen DOT de> <558DD1F3 DOT 4010301 AT cornell DOT edu> <20150627145259 DOT GB23036 AT calimero DOT vinschen DOT de> <20150630195547 DOT GG2918 AT calimero DOT vinschen DOT de> <5592F86E DOT 8070803 AT cornell DOT edu> <20150701104748 DOT GH2918 AT calimero DOT vinschen DOT de> <20150701135749 DOT GN2918 AT calimero DOT vinschen DOT de> <559449AF DOT 9010804 AT cornell DOT edu> <55949D9A DOT 7060900 AT cornell DOT edu> <20150702121301 DOT GA25423 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="RHdRtM27np9fZUoh"
Content-Disposition: inline
In-Reply-To: <20150702121301.GA25423@calimero.vinschen.de>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Jul  2 14:13, Corinna Vinschen wrote:
> On Jul  1 22:10, Ken Brown wrote:
> > I may have spoken too soon.  As I repeat the experiment on a different
> > computer, with a build from a slightly different snapshot of the emacs
> > trunk, emacs crashes when I type 'C-x d' with the following stack dump:
> >=20
> > Stack trace:
> > Frame        Function    Args
> > 00100A3E240  00180071CC3 (00000829630, 000008296D0, 00000000000, 000008=
2CE00)
> > 00030000002  001800732BE (00000000000, 00000000002, 00100A48C80, 000000=
00002)
> > 00000000000  00000006B40 (00000000002, 00100A48C80, 00000000002, 00100A=
48768)
> > 00000000000  21000000003 (00000000002, 00100A48C80, 00000000002, 00100A=
48768)
> > End of stack trace
> >=20
> > $ addr2line 00180071CC3 -e /usr/lib/debug/usr/bin/cygwin1.dbg
> > /usr/src/debug/cygwin-2.1.0-0.3/winsup/cygwin/exception.h:175
> >=20
> > $ addr2line 001800732BE -e /usr/lib/debug/usr/bin/cygwin1.dbg
> > /usr/src/debug/cygwin-2.1.0-0.3/winsup/cygwin/exceptions.cc:1639
>=20
> That points to a crash while setting up the alternate stack.  This is
> always a possibility because, in contrast to the kernel signal handler
> in a real POSIX system, the Cygwin exception handler is still running on
> the stack which triggered the crash up to the point where we call the
> signal handler function.  Dependent on how the stack overflow occured,
> this additional stack usage may be enough to kill the process for good.
>=20
> Out of curiosity, can you add this to the init_sigsegv() function:
>=20
>   #include <windows.h>
>   [...]
>   init_sigsegv (void)
>   {
>     [...]
>     SetThreadStackGuarantee (65536);

Of course this only works "per thread", so if init_sigsegv is called
for the main thread, only the main thread gets this treatment.  For
testing this should be enough, though.


Corinna

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

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJVlSyfAAoJEPU2Bp2uRE+ggyIP/19AQ3mKFmsDuSgmRWR5r2TD
M1s/u/e1bCyLuOhK+UWE3eLkNKtIQ8RmNizGn7SgTm2TP2Omi8KrPrKT9w6emaXx
yeH9LOLuzW88xU3OFP8pcM2mgkIEHqK2tt+Y7y4Tt8eQF16AIo+ooouQ6HNIv+5J
lTXM7CK/LJa75KPkO24wWf036y7BRA+c3Cq7zuWc2/+wxMRtvNktSHqPk/IcjgbV
KzkM9aZfbOoS2AuXLbmLP9rJYNvZqjiiYWH37/BSp1VUHHGLb1Y+hqoj2e+m3MzV
fZiCnqYaZhvm5tVISSjR+12RSpaRE1voeCieQrejOy8+3CZZqOyypZ1C/bHmIstH
BpuFW3wLoFXDYMShldXsNMLxWhTJfXyWOGg2axE5nbTX+GVqpsd8pH8zWHREKr+a
d0lV5holPihhnSn7yQaVbqKdzHbxS0qOQeVzEWn3bWclVgEeUZEVSeHTuarOtIx4
nyya9RSvqShv7XUza8UzjhtDywyAdM9nbclNS9wamJOm04RwRlcm89MARIEK3Y3I
Iy5oxZkOcVDeLoKeWChJROuJWMEL01jFK/dhFdEiRKr6TfTUaJjcYs7jbDBEW7E7
Y3Ffb01PHuS1WQW/SVARuSCtaEGcu+bxnNQg/BGLwGQ7iUuom5FFQLScUv/5eDiL
NaNibmom8Np4Kky4BjbA
=V0tv
-----END PGP SIGNATURE-----

--RHdRtM27np9fZUoh--