This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: emacs problem

On 7/10/2013 5:10 PM, Christopher Faylor wrote:
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
(  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

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.

Thanks. It's also possible that this isn't a Cygwin problem. There are known race conditions between emacs-24.3 and glib, which have been fixed in the newer version of emacs that I asked Dave to test.

Dave, instead of trying the new emacs right away, would you be willing to install the cygwin snapshot and see if that fixes the problem? If not, could you report the error message and then try the new emacs?



Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]