Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Sat, 20 Mar 2004 23:51:48 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Minimal test case for Make crash bug Message-ID: <20040321045148.GA14917@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <405C00BF.3090507@kegel.com> <405C06C4.7030508@kegel.com> <405C6C4B.90409@kegel.com> <405C939E.5020909@kegel.com> <405D1ACD.4060809@kegel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <405D1ACD.4060809@kegel.com> User-Agent: Mutt/1.4.1i On Sat, Mar 20, 2004 at 08:32:13PM -0800, Dan Kegel wrote: >It's all a bit mysterious. Where's a good place to look for clues? >I've already tried shutting down as many systray programs as I can... Build a debugging version of cygwin, use CYGWIN=error_start:..., type 'c' when gdb pops up, and then inspect like pointers, 'this' pointers, etc. -- Christopher Faylor Cygwin Project Leader Red Hat, Inc. -- 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/