X-Spam-Check-By: sourceware.org Date: Sat, 22 Jul 2006 18:30:39 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.20: Occasional crash at address 0x6100365f (cygthread::stub() in cygthre Message-ID: <20060722223039.GD18054@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060720193027 DOT GA14980 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Sun, Jul 23, 2006 at 03:55:05AM +1000, Kiyo Kelvin Lee wrote: >Now it seems the crashes are relating to another problem reported >earlier: 1.5.20: Occasionally infinite loop happens in do_exit() >(dcrt0.cc) (see attached original text below) > >I managed to make sure the infinite loop had not happened (more about >that later) and then tested to run configure for squid-2.6 multiple >times (ran for 2 hours) and was unable to reproduce a single crash. > >So I am guessing the infinite loop and hence explicitly killing the >offending process would leave cygwin in some funny state and lead to >those crashes. If you can reproduce the crash with the latest snapshot then please try including error_start:c:/cygwin/bin/gdb.exe in your CYGWIN environment variable as I previously suggested. This must be used before you start any other CYGWIN processes. If it works, then it should be fairly easy to see what the state of cygwin is when the crash occurs. FWIW, the loop in tty::terminate was reported as fixed in the latest snapshot. 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/