Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 4 Mar 2004 08:50:12 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT 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 AT cygwin DOT com References: <1078389549 DOT 4046eb2d54245 AT scso DOT 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 AT cygwin DOT com 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/