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: 6 Sep 2001 14:47:47 -0400 Message-ID: <20010906184747.20476.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com CC: cygwin-developers AT cygwin DOT com In-reply-to: <20010906203947.Q537@cygbert.vinschen.de> (message from Corinna Vinschen on Thu, 6 Sep 2001 20:39:47 +0200) Subject: Re: Figured out how to reproduce vfork/rsync bug! References: <20010906142836 DOT 7323 DOT qmail AT lizard DOT curl DOT com> <20010906164756 DOT 19885 DOT qmail AT lizard DOT curl DOT com> <20010906203947 DOT Q537 AT cygbert DOT vinschen DOT de> > Date: Thu, 6 Sep 2001 20:39:47 +0200 > From: Corinna Vinschen > > Nothing special. It just said BOOOOM! Ah. Did I forget to mention that sometimes this bug kills *all* your cygwin processes, not just the processes that fail. Sorry about that :-). I can't tell you how pleased I am to hear that you've managed to duplicate the problem. Now I don't feel so lonely anymore. Incidentally, I've managed to isolate it to something that was checked in between July 16 and July 17 (i.e., between "cvs update -D7/16/2001" and "cvs update -D7/17/2001"; I'm not sure whether that uses midnight local time, time on the CVS server or GMT). I'll let you know as I find out more. > I still have to examine the stackdump... You mean it's actually possible to derive useful information from those stackdumps? I've not been able to find anybody here who knows how to do that. Do tell. jik