X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type; q=dns; s=default; b=NldIzdPUu+iFwuXw so3LJ4OlYZ7zy+a3sT4d9UZXK39Lo3DVy5SExfsFl1Wx/tcn866/40Yu6AOaZrQF 11xhTBLT1icz4qoCUOG9pl1xX+LYaBKn7mYC9f6KNkzMkD9/9vlNE8TjdB1LQ/po uWl3bF8UaAj1QZI+3HeOEFqtdU0= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type; s=default; bh=ehQCrpvU9FwnPD69w7YxyY Znj3k=; b=nsDHKRa4K1betiV5yoYA6ivpIB+trXIRnuE5GkMmW0cMdicOy+no+F w1afjsL5JqsSat3U8d/7v8+C2qu3BeKgCQY7rfG+04NkSbHp4RQt2kxwd5++tEoq N+FWRp+vOy0admQ4ppaUr9pPjDDYmAFA/Dq9ezdcvYXw5slHKka0Q= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_00,FSL_HELO_BARE_IP_2,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 To: cygwin AT cygwin DOT com From: david AT adboyd DOT com (J. David Boyd) Subject: Re: emacs problem Date: Wed, 10 Jul 2013 15:07:01 -0400 Lines: 28 Message-ID: References: <51DDAE03 DOT 2040209 AT cornell DOT edu> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.1299999999999999 (Gnus v5.13) Emacs/24.3 (cygwin) Ken Brown writes: > 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 > > http://cygwin.com/ml/cygwin/2013-07/msg00062.html > > Ken Yes, the first thing I tried was rebaseall, but that also gives (in my history) the message about not being able to fork a new process. I'll get your rebuilt verison, and see what happens. It's worth a shot. Thanks, Dave -- 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