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=qTV3U2m3wYj8wX8tF7bpU3iY7gnUjT4GDnqfuVr0xS37z+QHOA94H
	3qCxoIdYNqPpunlIgnYF33n/n7f6+G820nvN6B01rLfdVuJZcGq6fiJg6S42PHc4
	tcifdwamLQSckxrl4mIAaK1syzoBVBgZh3tZkC/XBEst3m3ppsmPCc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Fri, 1 Aug 2014 15:32:25 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: (call-process ...) hangs in emacs
Message-ID: <20140801133225.GD25860@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <53DB8D23.7060806@alice.it> <CAK9Gx1cjj-7cDP7CunD7Bxz35L+SU9+4Ro3HRot5cwjcArudOA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="oIKd4Ysag+ysiDHn"
Content-Disposition: inline
In-Reply-To: <CAK9Gx1cjj-7cDP7CunD7Bxz35L+SU9+4Ro3HRot5cwjcArudOA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Aug  1 14:17, Peter Hull wrote:
> On Fri, Aug 1, 2014 at 1:50 PM, Angelo Graziosi
> <angelo.graziosi@alice.it> wrote:
> > Since I upgraded to Cygwin-1.7.31*, I see similar issue in building Ema=
cs
> > trunk (--with-w32 build)... The build always hangs in compiling some .el
> > file. CTRL-C does not work and I have to search the running processes w=
ith
> > "ps" and kill them with 'kill -9'. Downgrading to 1.7.30, things work
> > better. Now I am using 1.7.30...
> By better, do you mean 'perfectly'? It seems like it might be a little
> bit intermittent, from the reports I have seen.
>=20
> It's easy enough to do a cvs rdiff between the releases if 1.7.30 is
> known to be good - I am happy to help but I am unfamiliar with the
> code so I don't know where to start looking...

It could be a problem with the new default pthread mutexes being
NORMAL, rather then ERRORCHECK mutexes.  Somebody would have to
debug it...


Corinna

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

--oIKd4Ysag+ysiDHn
Content-Type: application/pgp-signature

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

iQIcBAEBAgAGBQJT25bpAAoJEPU2Bp2uRE+gcR0P/0VTBCxYmZgsClsHgwWLN2zb
U7z9M/JgnaOrP/VXrEQCe1qaGgds0qPxjgek41S7rpRzm6IwlScWn67wNg7d4GVV
G2s4rvxSWhAl4Nt+jM7rRloBKqCddVQONOlNt+Hci8Ghsu9dxWWr+pKjwSkUq1ZA
RE4D68r2Nno8udDMLeooxnFPvFs38bCbAmq08V0yJhSEuQYHnf3kJEKlJNLJSvcR
swGu1p0c3gbKE3g404nI5dkkfSg+4C5Gm9S7lg0WedeNOphny19Nh9uSdMWj+iyN
UAXOsoloq7gaOe1mU8V/WVFlVJKecxro1/+86/5GvM09q+RWjdB3stctecclAMFV
B2DZuyC43jeoxqcDa9tbx9gy3xqUFiOnn0d3UNMX0VyAlRvmR7B/EWV6oxwPSEcK
G6q4vMJdrFD480fz+L2qcjLEExFZygCStp7nDrgp/dT006b3N8NXvggEOr9Y/2bp
Wamd/pWd28Fl7qKtE10/e959d+jRRxn9Jlf9SYlk+qrKMgVu+lKZYqYHQz8s8iQ6
9kC6QYph2OeSWkaR2gv2r8ai7R2o8ZkVVEn6/mJUG1GXz7qA7h97bYRlXVTNmYcE
bdeT4QgpTYZ2QO4lXxTmtFGfMxBiCxhkpLnkL9KX5nwlAphxyvKLNr/GBtmDl3Fr
Qytz63TzPXvon//BFgnw
=s9Bg
-----END PGP SIGNATURE-----

--oIKd4Ysag+ysiDHn--