X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <4E57A03D.9050207@cs.utoronto.ca> Date: Fri, 26 Aug 2011 09:31:41 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: fixing fork failures (was: Re: Best way to repair cygwin?) References: <1314364947.32397.140258134011589@webmail.messagingengine.com> In-Reply-To: <1314364947.32397.140258134011589@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 26/08/2011 9:22 AM, Ronald Fischer wrote: > 9420794 [main] sh 8004 exception::handle: Exception: > STATUS_ACCESS_VIOLATION > sh: fork: retry: Resource temporarily unavailable > I had run setup again yesterday evening > I wonder whether there is an easy way to "repair" Cygwin Quoting Larry's recent response regarding a different symptom of the same underlying problem: On 23/08/2011 10:41 PM, Larry Hall (Cygwin) wrote: > This is typically the result of one of two things: > > 1. > > 2. DLL collisions - Install the 'rebase' package, read its README in > /usr/share/doc/Cygwin, and follow the instructions there to run > 'rebaseall'. Ryan -- 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