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:	Sat, 15 Sep 2001 22:07:42 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: make stackdumps
Message-ID:	<20010915220742.B29496@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3BA24EA6 DOT 683 DOT 1497CD06 AT localhost> <3BA24EA6 DOT 683 DOT 1497CD06 AT localhost> <4 DOT 3 DOT 1 DOT 2 DOT 20010915152210 DOT 041d3ed0 AT mail DOT interwoven DOT com>
Mime-Version:	1.0
In-Reply-To:	<4.3.1.2.20010915152210.041d3ed0@mail.interwoven.com>
User-Agent:	Mutt/1.3.21i

On Sat, Sep 15, 2001 at 03:52:47PM -0700, Hayden Ridenour wrote:
>I haven't seen the entire discussion on the stackdumps occurring in
>recursive makes but wanted to share a piece of information with those
>interested in the topic.  I've been encountering the problem for months
>and have been using the same solution as apparently a lot of others,
>running the target twice.  Like others, I am seeing the problem in
>rlogin or rsh sessions as opposed to bash shells opened directly on the
>machines.

Running the make twice does not really constitute excessive amount of
detail.  Since the crash is random, it would be common sense to restart
the make.

Sorry, this detail really is not going to help me track down the problem.

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/

- Raw text -