From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23765 invoked by alias); 4 Mar 2004 15:50:32 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 23679 invoked from network); 4 Mar 2004 15:50:28 -0000 Received: from unknown (HELO redhat.com) (66.187.230.200) by sources.redhat.com with SMTP; 4 Mar 2004 15:50:28 -0000 Received: by redhat.com (Postfix, from userid 201) id A5C66400016; Thu, 4 Mar 2004 08:50:12 -0500 (EST) Date: Thu, 04 Mar 2004 17:25:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1 Message-ID: <20040304135012.GA18643@redhat.com> Mail-Followup-To: cygwin@cygwin.com References: <1078389549.4046eb2d54245@scso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1078389549.4046eb2d54245@scso.com> User-Agent: Mutt/1.4.1i Reply-To: cygwin@cygwin.com X-SW-Source: 2004-03/txt/msg00235.txt.bz2 On Thu, Mar 04, 2004 at 10:39:09AM +0200, Michael Brand wrote: >I disabled one of the CPUs on my dual-CPU Xeon, and everything started working >well, so I guess this is a dual-cpu problem. My main development machine is a dual-CPU P3 and I have never been able to duplicate your problems. >Incidentally, I tried running my scripts on several dual-CPU Xeons (different >computer models, but all of them HPs), and though the crashes are not quite as >common elsewhere, and are therefore harder to localize into single-line >scripts, when I leave one of my involved scripts to crunch the CPU overnight, >it generally crashes an hour or two later, at the most. > >Hope this new information helps, I think it's safe to say that bug reports of the order of "I ran it for a while and then it crashed" are never all that helpful. What is always helpful is actual debugging of the problem. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/