Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 9 Oct 2001 23:06:56 -0400 From: "'cgf@redhat.com'" To: cygwin@cygwin.com Subject: Re: GDB breaks in 1.3.3-2 on certain Win2000 machines -- something to try Message-ID: <20011009230656.A15171@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <30BDEE18E474D511BB0A00D0B7BB87AF09294A@camel.mha.ca> <20011009212908.A30223@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011009212908.A30223@redhat.com> User-Agent: Mutt/1.3.21i Just in case this got lost in my previous long-winded email, it would be helpful if people could try the latest cygwin snapshot and report if the problem has changed. It would be even more helpful if people could build a debugging version of cygwin and report on the gdb stack trace, if it still fails. I suspect that it *will* still fail as I didn't really do anything substantial that would have fixed the problem. However, the stack trace should now be slightly more informative. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/