DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:date:subject:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=W5VockQKIUhjss9uv6EE8f7me8Kqv
	bIziYMbj39s8RHsvcUXmpQU2+iF82Gd0mN++78BiPVeXsKAAy2C9LvqNC3IYfMu7
	Na6snI1IvmQskYB2/QuzytIhXCc9rhdkXBexB5Jc3TWZI1s1vBl43kftBucyKKPB
	yAsOMk5M7x8fnI=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Date: Tue, 26 May 2015 09:57:11 -0400
Subject: RE: Doing vfork: resource temporarily unavailable
Message-ID: <edbc68784f8747d0bb532f3a2b44f181@vsrv060ex01.ssd.fsi.com>
References: <86pp5vlfwq.fsf@example.com> <555C8066.8080009@cornell.edu>	<CAK-n8j41UL6x867NUb3ZBrEkWiyQcC7+a1J7Qwa_yuTv=+MyUA@mail.gmail.com>	<3d9c900f406e4f4289c23e8f14b9304b@vsrv060ex01.ssd.fsi.com> <vriu4mmzvj65.fsf@example.com>
In-Reply-To: <vriu4mmzvj65.fsf@example.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

>To: cygwin@cygwin.com
>Subject: Re: Doing vfork: resource temporarily unavailable
>
>"Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com> writes:
>
>>>-----Original Message-----
>>>From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On
>>>Behalf Of Jim Reisert AD1C
>>>Sent: Wednesday, May 20, 2015 8:54 AM
>>>To: cygwin@cygwin.com
>>>Subject: Re: Doing vfork: resource temporarily unavailable
>>>
>>>> This indicates that you need to run a full rebase
>>>> (https://www.cygwin.com/faq.html#faq.using.fixing-fork-failures).
>>>> The simplest way to do this is to run '/usr/bin/rebase-trigger
>>>> full', then stop all Cygwin processes and services, and then run setup-x86.exe.
>>>> The _autorebase postinstall script will then take care of the rebase.
>>>>
>>>> I have occasionally found it necessary to reboot the computer before
>>>> doing this.
>>>
>>>This doesn't always work for me.  In fact, I just did this - set the
>>>trigger, rebooted, then ran Cygwin Setup.  The first time I started Emacs,
>>>no problem (only one dbus warning).
>>>The very next time, this:
>>>
>>>      0 [main] emacs-X11 2512 child_info_fork::abort:
>>>C:\Cygwin\bin\cygMagickCore-6.Q16-2.dll: Loaded to different address:
>>>parent(0x1710000) != child(0x1920000)
>>
>> Recently I spent about an hour running numerous rebaseall commands
>> interspersed with at least one rerun of setup-x86 and 3 reboots before my emacs vfork errors went away.
>> I don't know if it was the third reboot or something else such as
>> deleting some of my biggest emacs buffers ( I use desktop-save-mode) that finally cured the problem.
>> If there is a "bottom" to this problem I would be willing to participate as a tester.

>The autorebase did not work for me, even after several trials.

>I finally de-installed Cygwin, and reinstalled it (in its 64bit version which I did not use up to now).
>Now everything is back on track. Thanks.
>Best regards,
>  Seb
>--
>Sebastien Vauban

Instructions above state running setup-x86.exe not setup-x86_64.exe.
Does anyone experience frequent emacs vfork errors running 64-bit Cygwin?
Maybe it's time for me to try running that again?

What I've successfully done, twice :-), to fix my vfork errors is to follow the
above procedure: run rebase-trigger, stop all Cygwin, then run setup-x86.exe,
followed by a reboot, then bring up cmd window where I run,
cd c:/cygwin; cd bin; ash; /usr/bin/rebaseall -v

--
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