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: 14 Sep 2001 15:58:48 -0400 Message-ID: <20010914195848.8342.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com CC: cygwin-developers AT cygwin DOT com In-reply-to: <20010914155611.A16943@redhat.com> (message from Christopher Faylor on Fri, 14 Sep 2001 15:56:11 -0400) Subject: Re: Useful details about the Make SEGVs References: <20010912173945 DOT 25925 DOT qmail AT lizard DOT curl DOT com> <20010914002450 DOT B25486 AT redhat DOT com> <20010914170318 DOT 4862 DOT qmail AT lizard DOT curl DOT com> <20010914131117 DOT D2709 AT redhat DOT com> <20010914171959 DOT 5066 DOT qmail AT lizard DOT curl DOT com> <20010914192013 DOT 7730 DOT qmail AT lizard DOT curl DOT com> <20010914155611 DOT A16943 AT redhat DOT com> > Date: Fri, 14 Sep 2001 15:56:11 -0400 > From: Christopher Faylor > > The process is looping in make, pid 204 but not all of the information on > this process is in the strace log. > > So, I guess you could post that. No guarantees, though. When I can spend some more time looking at this, I'll try to duplicate the problem again, attach to the looping process and see if I can figure out anything new. But (a) I don't know how soon that'll be, and (b) like you said, if the stack is getting trashed somehow, it's not obvious that it's going to be possible to debug this in gdb. Sigh. jik