Doing vfork: resource temporarily unavailable

Rockefeller, Harry
Tue May 26 14:29:00 GMT 2015

>Subject: Re: Doing vfork: resource temporarily unavailable
>"Rockefeller, Harry" <> writes:
>>>-----Original Message-----
>>>From: [] On
>>>Behalf Of Jim Reisert AD1C
>>>Sent: Wednesday, May 20, 2015 8:54 AM
>>>Subject: Re: Doing vfork: resource temporarily unavailable
>>>> This indicates that you need to run a full rebase
>>>> (
>>>> 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:
Unsubscribe info:

More information about the Cygwin mailing list