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:date:from:subject:in-reply-to:to:cc:reply-to
	:message-id:references; q=dns; s=default; b=pp9/sb8E+Eeir3enH0V8
	ZomS+GjUsa1SmQjnNMRP31Ol5cES/hRBiYS3IowSu819hOQ4Va5qBxLiX77at1ho
	LDpKXUTSWD5PhJSCHLrAe0AP+z3w65mrLUhrjxZ03oSL5knTZAjo1FhjZbeLj00B
	m4YmD7IzFzqWcZHldwtjzNU=
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:subject:in-reply-to:to:cc:reply-to
	:message-id:references; s=default; bh=fuRqA/Z5H6IRy/6LudtdcwNoGD
	o=; b=oJZVTZQT1Zk32CjD/hyvl63k5w0x79PhzZqAKHp68MtHPpDk3O+BR8azHH
	dXg9fpgHHOOvn2imX1cLHzRRHnWk+zuON+R4JBtIB+saUqN6p/2+5jhFbdZPfnDo
	m6rsj5AwvD8pes7rLs9IMEhSshBQHsW3qv/LkGQdJDfB9eFTE=
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
X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,SPF_SOFTFAIL autolearn=no version=3.3.1
Date: Fri, 14 Jun 2013 21:16:44 +0300
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
In-reply-to: <51BB56CB.7030209@cs.ucla.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: cygwin@cygwin.com, 14569@debbugs.gnu.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83ppvov9pv.fsf@gnu.org>
References: <b4m61xqu654.fsf@jpl.org> <51B5DA82.4010703@alice.it> <3EC77598-24B8-42DD-8983-5069E64AAB60@swipnet.se> <51B62175.10307@alice.it> <06F80BBC-D7CD-4E6C-97AD-EB8E476E2FC0@swipnet.se> <83sj0olh38.fsf@gnu.org> <51B7717D.6060702@cs.ucla.edu> <51B77A00.2060908@cornell.edu> <83mwqwl903.fsf@gnu.org> <51B78346.3050600@cornell.edu> <FA9D25B7-3D1F-40CC-AA6E-5347E8112CA4@swipnet.se> <E143AC75-8C2B-4A59-81F6-571B9D4EEF13@swipnet.se> <2E06A322-530C-4AA2-9282-6D2E48B1D194@swipnet.se> <51B8BEFE.6070309@cs.ucla.edu> <51B8D5ED.1010407@alice.it> <C679A2B2-0264-4DDA-B900-5B90BE7CF1E9@swipnet.se> <51BA03CA.4080804@cs.ucla.edu> <BEC82502-E9FD-4F8E-B91E-F680F6885FB2@swipnet.se> <51BB56CB.7030209@cs.ucla.edu>

> Date: Fri, 14 Jun 2013 10:45:47 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: 14569@debbugs.gnu.org
> 
> Cygwin developers, I'm worried about a Cygwin bug where
> pthread_kill may not send a signal to the correct thread.
> This bug may be causing Emacs to crash.  The Cygwin bug is
> discussed in this thread:
> 
> http://cygwin.com/ml/cygwin/2012-05/msg00472.html

Caveat: I'm not a Cygwin developer, and don't even use Cygwin.

> Emacs uses pthread_kill to redirect
> SIGCHLD to the main thread; if this is sent to a random
> thread instead, that could explain the random crashes.

It should be easy to instrument deliver_child_signal so that it prints
something when it redirects SIGCHLD, and then the Cygwin users could
see if there's such a report immediately before the crash, or at all.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple