This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: emacs problem
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 10 Jul 2013 17:10:14 -0400
- Subject: Re: emacs problem
- References: <m9hik3kyjnk9 dot fsf at W0144758 dot usac dot mmm dot com> <51DDAE03 dot 2040209 at cornell dot edu> <20130710205538 dot GA5740 at ednor dot casa dot cgf dot cx>
- Reply-to: cygwin at cygwin dot com
On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote:
>On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote:
>>On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>>
>>> I'm starting to see this error quite a bit in the terminal window I started
>>> emacs from:
>>>
>>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>>> forked process - failed to create new win32 semaphore, Win32 error 87
>>
>>Have you tried rebaseall
>>(http://cygwin.com/faq.html#faq.using.fixing-fork-failures)? This isn't
>>the typical error message you see from rebase problems, but it can't
>>hurt to try. If that doesn't help, maybe you could test the build I
>>mentioned at
>
>That doesn't look like the standard fork problem, Ken. The error comes
>from semaphore::_fixup_after_fork:
>...
>Error code 87 is ERROR_INVALID_PARAMETER. The only two things that I
>can see which would cause that problem are "sec_non_nih" and
>currentvalue.
>
>I'll change the error to report on currentvalue. I assume that
>currentvalue must be zero for some reason here and that is what is
>causing the problem but it would be nice to know for sure.
The current snapshot has this change and a shot-in-the-dark attempt to
fix the reported problem as well.
cgf
--
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