Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 11 Sep 2001 20:21:30 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: make.exe stackdump from "make -j2" with current CVS source Message-ID: <20010911202130.A490@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20010912001650 DOT 20683 DOT qmail AT lizard DOT curl DOT com> <20010912001801 DOT 20694 DOT qmail AT lizard DOT curl DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010912001801.20694.qmail@lizard.curl.com> User-Agent: Mutt/1.3.21i On Tue, Sep 11, 2001 at 08:18:01PM -0400, Jonathan Kamens wrote: >Oh, I forgot to mention.... Whatever the problem here is, I doubt it's >new to 1.3.3, since we've seen occasional make.exe stackdumps before >(I didn't report details about them because I didn't know how to debug >them and because dumper.exe wasn't yet available to get crash dumps). >So unless someone else thinks this is new to 1.3.3 and should be >investigated further, it shouldn't hold up 1.3.3. I don't know if it is new to 1.3.3 but it has been previously reported and extensively discussed here in the last week. It might be useful to set error_start_init to run gdb so that you can actively debug the process when it dies. This has also been discussed here recently. cgf