Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
To: cygwin@cygwin.com
X-Injected-Via-Gmane: http://gmane.org/
Path: not-for-mail
From: "Joseph H. Buehler" <aspam@cox.net>
Newsgroups: gmane.os.cygwin
Subject: Re: Long Shot, Mostly OT Compiler / System Crash Issue
Date: Fri, 02 Aug 2002 21:45:30 -0400
Lines: 15
Message-ID: <3D4B35BA.9080105@cox.net>
References: <5.1.0.14.2.20020802095340.02b9cb38@pop3.cris.com>
NNTP-Posting-Host: ip68-100-179-154.nv.nv.cox.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: main.gmane.org 1028339093 4038 68.100.179.154 (3 Aug 2002 01:44:53 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Sat, 3 Aug 2002 01:44:53 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529
X-Accept-Language: en-us, en
X-Enigmail-Version: 0.63.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime

Randall R Schulz wrote:

> Can anyone offer any suggestions about how to try to ascertain the 
> problem (with an eye toward finding a work-around, of course). I can't 
> really afford to replace the system right now and apart from this 
> repeatable hang, the system is reliable enough for me to live with, even 
> if I dislike its instability it a lot.

Try varying the compilation options, especially -O vs. without.

I believe that there are also two compiler for Cygwin -- gcc 2.95
and gcc 3.1.  You might try whichever one you are not using.

Joe Buehler




--
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/

