From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: emacs problem
Date: Wed, 10 Jul 2013 21:10:00 -0000 [thread overview]
Message-ID: <20130710205538.GA5740@ednor.casa.cgf.cx> (raw)
In-Reply-To: <51DDAE03.2040209@cornell.edu>
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:
void
semaphore::_fixup_after_fork ()
{
if (shared == PTHREAD_PROCESS_PRIVATE)
{
pthread_printf ("sem %p", this);
/* FIXME: duplicate code here and in the constructor. */
win32_obj_id = ::CreateSemaphore (&sec_none_nih, currentvalue,
INT32_MAX, NULL);
if (!win32_obj_id)
api_fatal ("failed to create new win32 semaphore, %E");
}
}
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.
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
next prev parent reply other threads:[~2013-07-10 20:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 19:07 J. David Boyd
2013-07-10 19:14 ` Ken Brown
2013-07-10 19:19 ` J. David Boyd
2013-07-10 20:55 ` Ken Brown
2013-07-10 20:59 ` J. David Boyd
2013-07-10 21:10 ` Christopher Faylor [this message]
2013-07-10 22:13 ` Christopher Faylor
2013-07-10 22:28 ` Ken Brown
2013-07-10 23:18 ` Christopher Faylor
2013-07-11 15:07 ` J. David Boyd
2013-07-11 15:23 ` Corinna Vinschen
2013-07-23 15:13 ` Ken Brown
2013-07-23 19:23 ` J. David Boyd
2013-07-23 19:54 ` J. David Boyd
2013-07-24 13:22 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 12:45 Emacs Problem Dieter Meinert
[not found] <34385CBC5E8E664EB0007814636AB36A677AA2@exchange1.dimension s.com>
2003-01-15 22:13 ` Larry Hall (RFK Partners, Inc)
2003-01-16 0:19 ` Igor Pechtchanski
2003-01-15 22:04 Scott Purcell
2003-01-15 22:18 ` Frank Schmitt
2003-01-15 23:49 ` Randall R Schulz
2003-01-16 10:19 ` David Starks-Browning
2002-10-14 18:50 emacs problem Vincent Yau
2002-10-15 13:40 ` Joe Buehler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130710205538.GA5740@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).