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: Sat, 15 Sep 2001 22:07:42 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: make stackdumps Message-ID: <20010915220742.B29496@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3BA24EA6.683.1497CD06@localhost> <3BA24EA6.683.1497CD06@localhost> <4.3.1.2.20010915152210.041d3ed0@mail.interwoven.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/