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 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: <1077554594.403a2da21a1ef@scso.com> Date: Mon, 23 Feb 2004 18:43:14 +0200 (IST) From: Michael Brand References: <1077541378 DOT 4039fa02c97f9 AT scso DOT com> In-Reply-To: <1077541378.4039fa02c97f9@scso.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.6 X-Originating-IP: 212.179.66.75 Hello, Regarding your question, Corinna, I am using Cygwin's latest stable (the one you get when you download and install current versions of packages). I am considerably more interested in a stable system than in a "state-of-the-art" system, which is why I am avoiding the use of snapshots. However, I have other developments regarding this problem: I have managed to reproduce the problem now in a "bash" script as well. It still uses plenty of "sed"s, but the hang happened in a call to "basename". I am beginning to believe that this problem has to do with a misbehavior of Cygwin on dual-CPU machines / on Xeons / on dual-Xeon machines. Any feedback, but especially from people with experience using Cygwin on such platforms, will be much appreciated. Thank you, Michael. Quoting Michael Brand: > The problem started appearing when I switched to using HP Proliant ML330 > G3 > dual-Xeons. > > I have now localized the problem, producing a tcsh script with only one > line that causes a hang if run enough times: > > set b=`echo a | sed 's/a/b/'` > -- 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/