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:message-id:date:from:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=uP6TIhTtiutBHLah
	dKKYlYzMZ9GxOPSh2ehBq9/cq2U+9zbj/8QpbG5vyhB3I2t0lGa0h0QQg9ns1Rx8
	/T1/m+yhzt0AkhunkcoMH9BZATxWch23dVYmKh8esztAcMRy6AwP9vKdQk1oMDnf
	a3joSX7MKJd8ddyGGYln/rft+r8=
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:message-id:date:from:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=DoCoWd3PAO4BkxaVhdIbLr
	ZU87Y=; b=sx+oi9jrbuCnFKAkyx9TMHDDsO55g5eQH01HVu/quGr7af8At4ZcWS
	cEYD6D1NEbzCnYDroXlKVak41VV9Znw0M40iyMDnwOMZfZJuMAP2ZZ0NhMqqw1jC
	AhlIdk3nlPMvE4F7jzwiTeoXfpulGbqkDyPsOUlPl4AIbkemMvQTM=
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=-5.6 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_MED,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.1
X-CornellRouted: This message has been Routed already.
Message-ID: <51BB7B82.4010204@cornell.edu>
Date: Fri, 14 Jun 2013 16:22:26 -0400
From: Ken Brown <kbrown@cornell.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: cygwin@cygwin.com
CC: 14569@debbugs.gnu.org
Subject: Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
References: <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> <20130614180359.GA5295@ednor.casa.cgf.cx>
In-Reply-To: <20130614180359.GA5295@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 6/14/2013 2:03 PM, Christopher Faylor wrote:
> On Fri, Jun 14, 2013 at 10:45:47AM -0700, Paul Eggert wrote:
>> 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
>>
>> 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.
>>
>> My question is: does this bug still exist with Cygwin,
>> and if so is it likely to get fixed soon?
>
> You pointed to an archived mail messages which implies that was fixed
> more than a year ago.  What makes you think it is still a problem?
>
> I'd expect that if it was still a problem our emacs maintainer would
> be on top of it.

Unfortunately, the emacs maintainer doesn't have any idea why the recent 
emacs changes are causing random crashes on Cygwin.  It's almost 
impossible to catch this under gdb; and the one time it was caught, the 
backtrace didn't make sense.  Also, the crash doesn't occur when emacs 
is run under strace.

I'm not going to speculate on whether the problem is caused by a bug in 
Cygwin's pthread_kill.

Ken

--
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

