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=h4gRJlrGI/kM8EC7zhCZqT09DAcSWc3lLgEdK9irPcs0/4BWlALeW
	XIDvv6jFOxRJTHe2IkHhjWCLKJvCmNQyETjEADo3yb3JnKQ+hAFVUQeX4xwyyWrT
	jSwvlTFc8urdpNBItqFKtBDJD1Vf5H4Zm6c7UHIJEjfiY4J579kmx4=
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=FDlgO74VEvyV9cUB600RB1zidhQ=; b=n8HiLhxsyjFgNU9v7h9iD5kf8ZSL
	5aX3qNplIkGRxXc447DrqQTf08P8UjN1VRTTDMIJVcugkiPER0zAgmLcq+danaGX
	VASdPpRSv1kVY7Jcy1sYhwXO4pZb+htPZVw/ZSq0PWqDU6E3VASJa1V9oU6/4D9S
	eWovKq63NuWnTls=
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
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE autolearn=ham version=3.3.1
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/G0PfYyZwkh4ey1xjMhqCJ
Date: Fri, 14 Jun 2013 14:03:59 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
Message-ID: <20130614180359.GA5295@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <51B78346 DOT 3050600 AT cornell DOT edu> <FA9D25B7-3D1F-40CC-AA6E-5347E8112CA4 AT swipnet DOT se> <E143AC75-8C2B-4A59-81F6-571B9D4EEF13 AT swipnet DOT se> <2E06A322-530C-4AA2-9282-6D2E48B1D194 AT swipnet DOT se> <51B8BEFE DOT 6070309 AT cs DOT ucla DOT edu> <51B8D5ED DOT 1010407 AT alice DOT it> <C679A2B2-0264-4DDA-B900-5B90BE7CF1E9 AT swipnet DOT se> <51BA03CA DOT 4080804 AT cs DOT ucla DOT edu> <BEC82502-E9FD-4F8E-B91E-F680F6885FB2 AT swipnet DOT se> <51BB56CB DOT 7030209 AT cs DOT ucla DOT edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51BB56CB.7030209@cs.ucla.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)

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.

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