This is the mail archive of the
mailing list for the Cygwin project.
Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Cc: 14569 at debbugs dot gnu dot org
- Date: Fri, 14 Jun 2013 16:22:26 -0400
- Subject: Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
- 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> <20130614180359 dot GA5295 at ednor dot casa dot cgf dot cx>
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:
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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple