X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_YW,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4C7AC2D7.1020102@gmail.com> Date: Sun, 29 Aug 2010 21:28:07 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: BLODA diagnostics References: <20100827165751 DOT GZ10153 AT gremlin DOT foo DOT is> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 27/08/2010 21:44, mike marchywka wrote: > On 8/27/10, Baldur Gislason wrote: >> Hi, what tool is best to track down what BLODA is causing fork failures on >> my Cygwin installation? > There may be a sysinternals tool, I use those to track down open handles > that have been a problem on earlier systems. Sysinternals Process Explorer has a mode when it shows you all the DLLs loaded into a process. Any of these that come from security software or other installed applications (i.e. aren't part of the standard windows system DLLs) can give you a clue as to what's causing the BLODA. If that doesn't help, rebaseall might get things going again, if you haven't already tried it. (See /usr/share/doc/Cygwin/rebase-3.0.1.README for usage.) cheers, DaveK -- 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