"Rockefeller, Harry" <harry.rockefel...@flightsafety.com> writes:
>>-----Original Message----- >>From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@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 -- 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
