Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 21 Feb 2001 22:15:00 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Re: GCC untrackable crashes
Message-ID: <20010221221500.A8646@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
References: <711F6B80B5B4D211BA900090272AB7649C4211 AT noyce DOT eecs DOT berkeley DOT 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