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:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=xZ6AH
	ruFOPXH4sqtu21dH1d5Jxqjc2mCb+QixQ09OXTXiAD7RC0e3bJs2FLCQRRdW6iwn
	fTksHQW5OS6peX1/JxPTPDcFa9+Eff+3PIedY1nIh8nVmcRmXJ1fyQRkRjCf9P7p
	4YLvTEZgA+9jhHRoaTGexRQZEdT0ksJLLv/YKQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Doing vfork: resource temporarily unavailable
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>	<edbc68784f8747d0bb532f3a2b44f181@vsrv060ex01.ssd.fsi.com>
Date: Tue, 26 May 2015 18:39:47 +0200
In-Reply-To: <edbc68784f8747d0bb532f3a2b44f181@vsrv060ex01.ssd.fsi.com> (Harry	Rockefeller's message of "Tue, 26 May 2015 09:57:11 -0400")
Message-ID: <87vbff9tt8.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Rockefeller, Harry writes:
> 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?

DLL collisions are _much_ less likely on x86_64 out of the gate, but
they do occur from time to time.

> 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

That's the wrong procedure.  You run

rebase-trigger fullrebase

then reboot (if you have reason to suspect that a reboot might help,
then run setup.exe (either architecture).  An additional rebaseall
beyond that isn't going to do anything useful.  A full rebase on the
same installation is deterministic, it will always chose the same base
addresses.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

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