This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Paul Eggert <eggert at cs dot ucla dot edu>
- Cc: cygwin at cygwin dot com, 14569 at debbugs dot gnu dot org
- Date: Fri, 14 Jun 2013 21:16:44 +0300
- Subject: Re: bug#14569: 24.3.50; bootstrap fails on Cygwin
- References: <b4m61xqu654 dot fsf at jpl dot org> <51B5DA82 dot 4010703 at alice dot it> <3EC77598-24B8-42DD-8983-5069E64AAB60 at swipnet dot se> <51B62175 dot 10307 at alice dot it> <06F80BBC-D7CD-4E6C-97AD-EB8E476E2FC0 at swipnet dot se> <83sj0olh38 dot fsf at gnu dot org> <51B7717D dot 6060702 at cs dot ucla dot edu> <51B77A00 dot 2060908 at cornell dot edu> <83mwqwl903 dot fsf at gnu dot org> <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>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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