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: Wed, 21 Feb 2001 22:15:00 -0500 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: GCC untrackable crashes Message-ID: <20010221221500.A8646@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: <711F6B80B5B4D211BA900090272AB7649C4211@noyce.eecs.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <711F6B80B5B4D211BA900090272AB7649C4211@noyce.eecs.berkeley.edu>; from kcamera@bwrc.eecs.berkeley.edu on Wed, Feb 21, 2001 at 06:43:40PM -0800 On Wed, Feb 21, 2001 at 06:43:40PM -0800, Kevin Camera wrote: >Thanks for the tip. In fact, the debugger was in thread 1, and the only >other thread did not offer any other information. So unfortunately the >problem was with the compiler or debugger, since all threads had no trace >information. Hmm. As someone who uses the compiler and debugger on an almost daily basis I have to say that I have never seen this behavior on a program that was compiled with debugging info (-g). cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple