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=j/rjKuzG6uKcX5CrplgqrB4sEEL1QsFrdspWPj5VImN9sHJBGjdZU
	QUVds+AwiIe64qhFcPD7lA3qYt6gTb0Q6r2zkCl7cWvDWpi/sOJuKZevI8rmchuj
	PMbsvNHirIKcFcpsIWeGw1ZXa5WxCv8iuSrramd16tOSVafhH+l+4I=
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=AcVw4Jd6+OwehPGY+Y9bwehvQwo=; b=oA8LHVgnE/4UJml2ZcBFH0NYX+Gv
	CalJKQBiO393iiHyI1lwzwPuwgsIqqXWHxUhnZqJfnjoq955Zz6L+nD1fHRN/Hpe
	8Ul6vzoCbqIBTHp6w4hka1h8K7w03kO0Ftdk2OMGcRNH4jMc9e4LoxKobZj58rso
	Al2NSnkeZV1Ymps=
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=-2.1 required=5.0 tests=AWL,BAYES_50,KAM_BODY_URIBL_PCCC autolearn=no version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Mon, 4 Aug 2014 10:00:34 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: (call-process ...) hangs in emacs
Message-ID:	<20140804080034.GA2578@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<53DB8D23 DOT 7060806 AT alice DOT it> <CAK9Gx1cjj-7cDP7CunD7Bxz35L+SU9+4Ro3HRot5cwjcArudOA AT mail DOT gmail DOT com> <20140801133225 DOT GD25860 AT calimero DOT vinschen DOT de> <53DEDBBA DOT 20102 AT cornell DOT edu>
MIME-Version:	1.0
In-Reply-To:	<53DEDBBA.20102@cornell.edu>
User-Agent:	Mutt/1.5.23 (2014-03-12)

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

On Aug  3 21:02, Ken Brown wrote:
> On 8/1/2014 9:32 AM, Corinna Vinschen wrote:
> >On Aug  1 14:17, Peter Hull wrote:
> >>On Fri, Aug 1, 2014 at 1:50 PM, Angelo Graziosi
> >><angelo DOT graziosi AT alice DOT it> wrote:
> >>>Since I upgraded to Cygwin-1.7.31*, I see similar issue in building Em=
acs
> >>>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 =
with
> >>>"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.
> >>
> >>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.
>=20
> That does seem to be the problem, since I can reproduce the bug starting
> with the 2014-07-14 snapshot.  More precisely, I can reproduce it using
> emacs-nox (which is what the OP was using according to his cygcheck outpu=
t)
> but not using emacs-X11 or emacs-w32.
>=20
> I tried running emacs under gdb with a breakpoint at call_process, but al=
l I
> could see from that is that emacs tries to fork a subprocess, but the call
> to fork() never returns.  I also tried running it under strace, but again
> all I can see is that fork() is called and then everything seems to be at=
 a
> standstill.
>=20
> Corinna, if you want to take a look, here's the precise recipe:
>=20
> 1. emacs-nox -Q [This should start emacs and put you in the *scratch*
> buffer.]
>=20
> 2. Enter the following text into the buffer:
>=20
>   (call-process "pwd" nil t)
>=20
> 3. Position the cursor at the end of the line and type Ctrl-j.
>=20
> What should happen, and what does happen prior to the 2014-07-14 snapshot,
> is that the current directory is displayed, followed by the exit code of =
0.
> What happens instead is that emacs appears to hang.

How does emacs start a process?  Does it create a thread and then
forks and execs from the thread?  Does it use its own pthread_mutex
to control the job?  Is there a chance to create an STC of this
process?


Thanks,
Corinna

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

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

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

iQIcBAEBAgAGBQJT3z2iAAoJEPU2Bp2uRE+gregQAIaHMtUi3kyxC97Hc8bcvrAt
fBno/FXTpNssrUo87GGFpSfKFlU1wHC/pmdrHvi3poFW0mrZD3Y1WHnQWl8Y0KU5
I13zgTmSayvX65k4vwypE+NdysLRCa2c1HpcKCCZ+pdNyQJu5UudjLlE7wHkYx8D
5bEYhcGRRdz5BFlcUNmjUKz4o9gvRTA3IP9W6H09eBK4DNONoe4/C0HJ1x9rGWX+
+epCBajGPbgMvhGzsFY+ENuoVEzd1M2BS94SUieYubBxZUhgB7TTq+iqwsE72qrN
v0YNxLKv7wC7JWRQdaRjgORaU28yWLoCYjx230Rdb3YbED4jiHxSBYyS7Jz/LxRO
i4UEaE27Z1kpIxxNur5UrFLq3xAEF24+OLPLgP44n8FZF+ztaLPgkY2XpkB1DRGQ
fdETmccfUBcDEXnIS8bjMwGLBfewDL8fXRCD9a9kxS4vf4tR+d4KSueI923ObXeB
k3+yutQBL+lX3C+tu2EJBlxKCJumtSMu+V23n4pdz44CFUakpZXlZD36OvGyx1Qt
z2ExGDqWNyt5XjASOuJxjKmmcaYF/V7lOV33tQE/GEgjCaSqS/qdq5a6tYMWicZ2
fk1fzNKdgV7zwK4bO2T/WjBrM/fhg9pNQoMWgyUcXoNxgWjmWneAJ6IsoJEUV8/d
FApy5MNjUXgfeLdnIAML
=phuP
-----END PGP SIGNATURE-----

--gBBFr7Ir9EOA20Yy--

- Raw text -