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=XrZDpw8YqtAADi093wqvzzwcLwhIWy1X6aWk+kuwMr6Txk8tp5LVy
	1ki26daaSlUpxf72xm0tky62xCrK3VP62tMAlfH+pQSnjNF+PbBwcq66pdZsul4N
	Fd4pznRjTRBavDgP99LcCNORCnCWt6VO5yXcljkwGITCUbTbdDaf+g=
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=vfEuqh3p3clDfKL5+UlXD64fJfk=; b=KzFyWMKh7ZYESPSwO/GI52BdLUR7
	8nW0ijxc/0xmDzlCygiKpCxMj0pBhqKMjj6ZgzZYNRYXvuZlWGvg+o2rPkeE1tpF
	YmbfG7x2Pyc7QaNrwaTiEsTiORg83OqKE3fRFAg2KZI1RLXhF/DQc/NvxafoOX9D
	RfxWo0DRyIHWTmc=
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:	Sun, 16 Mar 2014 12:53:07 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: With latest snapshot, emacs is very slow to start under X11
Message-ID:	<20140316115307.GC400@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<532325A5 DOT 5020103 AT cornell DOT edu> <53232E30 DOT 3080801 AT cornell DOT edu> <20140314164243 DOT GD2355 AT calimero DOT vinschen DOT de> <53234E31 DOT 8030805 AT cornell DOT edu> <20140314201916 DOT GG2355 AT calimero DOT vinschen DOT de> <53248149 DOT 2000007 AT cornell DOT edu>
MIME-Version:	1.0
In-Reply-To:	<53248149.2000007@cornell.edu>
User-Agent:	Mutt/1.5.21 (2010-09-15)

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

On Mar 15 12:35, Ken Brown wrote:
> On 3/14/2014 4:19 PM, Corinna Vinschen wrote:
> >The problem is this.  The memory addresses given in the straces or in
> >the below stackdump don't make any sense to me, because I don't have
> >your DLL.  For clarity it would be helpful to run
> >
> >   addr2line -e cygwin1.dbg [address...]
> >
> >so the addresses (the ones starting with 0x0018 at least) can be
> >conveniently connected to source lines.
>=20
> Sorry, I meant to say that the straces were made from
> cygwin-1.7.28-2 ("good DLL") and the 2014-03-10 snapshot ("bad
> DLL").  The addresses of the exceptions in the straces all point to
> thread.cc:144.  I can't do anything with the stackdump below
> because, as I said, I don't know which DLL I was using when the
> crash occurred.  All I know is that it was from one of the
> snapshots, because it happened while I was bisecting.
>=20
> I'll keep testing and see if I can get another stackdump.

Thanks.  What makes me wonder is the long time emacs is waiting
for dbus.  This doesn't make sense in terms of exception handling.
It sounds a bit as if it's *really* waiting for some reason and
the question is, what exactly is it waiting for (socket timeout?)
and why didn't it wait before?

> >>These three facts suggest that the problem might have something to do w=
ith how Cygwin handles an exception that occurs when emacs (or Glib) tries =
to start a dbus daemon and the latter crashes.  But I'm just guessing.
> >
> >But why does it crash in the first place?
>=20
> I have no idea.  I'll see if I can figure anything out.

That would be incredibly helpful.  There is a chance that the old
exception handling didn't work as expected and therefore covered
something under the hood.

> >Using the SEH filter is, strictly speaking, the right thing to do.  The
> >vectored exception handler is just an ugly workaround in comparison.
> >Therefore it's quite the bummer that emacs or dbus or whatever, seems
> >to choke on that.  I'm not familiar enough with exception handling so
> >I can't guarantee that I find a solution which is working in all cases.
> >I was glad enough when Kai Tietz (our Mingw64 maintainer) pointed out
> >the SEH filter solution used Mingw64.  I'm using it in exactly the
> >same way as Mingw64 is using it :(
> >
> >Why is it always emacs?  Vim works fine...
>=20
> Sorry.

Nah, never mind.  I'm just frustrated, is all.


Corinna

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

--qlTNgmc+xy1dBmNv
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJTJZCjAAoJEPU2Bp2uRE+ggncP/07uIVpOShAEEZ+UcqKn539q
8U6FFEFVmJubzD1rKN9sdPXVmTJ5c5OzfAVsR3gEkesZ/pLlheTZK3CGTbm/anLs
tPaGZwHDgSRocbkExJ+h7Th6kLnuacWF684sxnjM5brPBwlbt1c9NvsIYSY5M14B
qb1FBP6z+maYRwq2RHEQo5pY3KdGqp/HD+7mPQ9miOEPkDFNIaD3AiUc3UAJVkqn
d8YibOVTET+oq0V+AnGzrOkifp+Iu2vxLvzcYAiM41c8Rk+UaPuDvRnoWmiLWn/R
Y2YwEAqRDIK89uRWQ7HUsngnyePJYWQNIz//3ObnUXHJloFOWS879D0Ww8LIlxVd
FpjRTuOmBKMtjsX86OX3XwG34jmQl32EJg04hm29S9c60sEQSZxXEysC2oAZJq34
OTmwGzg66tgNxWAdKgxt/HO0KMQrH5oM9NLojK8fNeGyQpfrBNzZPFIkfIGyihkP
K3AM7+Gj+IOzE1/LCAxtoUt+K94vaKLEyCheTQwbKhv9IvI5tr4vtTGA6TzLCmwZ
NBsvxCXgMuypO1cF7xc+77UX5WM9WLjzLnXO4OEDlJuNwcXhmgVo+7ymt9d1gfcX
NDR/wgXZMdAP/Q85ewiaeNWeLXhjjbiRRAi0BdzLK0ZJBS5P3tMw40GJhCUrIjvA
DelvkVos5X785OS++9qY
=hJdG
-----END PGP SIGNATURE-----

--qlTNgmc+xy1dBmNv--

- Raw text -