X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 13 Apr 2009 21:45:42 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.5.25: cygwin executeables are crashing from time to time (Windows 2003 Server Ver 5.2 Build 3790 Service Pack ) Message-ID: <20090414014542.GA1681@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <33936.203.47.149.67.1239673160.squirrel@203.47.149.67> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <33936.203.47.149.67.1239673160.squirrel@203.47.149.67> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Tue, Apr 14, 2009 at 05:39:20AM +0400, Stefan Walter wrote: >The cygwin processes are crashing on the "Windows 2003 Server Ver 5.2 >Build 3790 Service Pack". It does not happen regulary, just sometimes but >then in series of lets say 5-10 exectuions. This happens on multiple >machines, all with the same OS, therefore i think it is a bug rather than >a setup problem. > >I have already removed cygwin and installed it fresh - this did not change >anything. > >i have seen the crashes for: bash, sh, ls, cp, ... > >Here are some examples of the Windows Event Log: > >Faulting application cp.exe, version 0.0.0.0, faulting module cygwin1.dll, >version 1005.25.0.0, fault address 0x00047699. > >Faulting application bash.exe, version 0.0.0.0, faulting module >cygwin1.dll, version 1005.25.0.0, fault address 0x00047699. > >Faulting application ls.exe, version 0.0.0.0, faulting module cygwin1.dll, >version 1005.25.0.0, fault address 0x00047699. > >NOTE: the address is always similar and points to something in the >cygwin1.dll. > > >Is there any workaround, or how can we fix this? This problem is critical >for us. The fault address of 0x00047699 is not in the cygwin DLL. You need to read the problem reporting guidelines at: http://cygwin.com/problems.html But, I suspect BLODA: http://cygwin.com/acronyms/#BLODA cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/