Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

fyi.. -- Forwarded message -- From: Michael Brand <[EMAIL PROTECTED]> Date: Feb 13, 2006 11:13 PM Subject: Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1 To: Stewart Midwinter <[EMAIL PROTECTED]> Cc: cygwin@cygwin.com Nope, I never found a good solution, and

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

On Mon, Feb 13, 2006 at 03:15:16PM -0700, Stewart Midwinter wrote: >From: Michael Brand brand.scso.com> >>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. > >> I tried running my scripts on several dual-CPU Xeons (differen

re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

From: Michael Brand brand.scso.com> >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. > I tried running my scripts on several dual-CPU Xeons (different > computer models, but all of them HPs), ... snip ... > it generally

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

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. >Incide

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

Hello again, 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. 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

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

At 01:28 PM 2/25/2004, Michael Brand you wrote: >Here's something that may help. > >I copied an ancient distribution of Cygwin (simple copy, no installation at >all) from another computer, and it seems to work fine on the dual-Xeon. > >I am attaching the cygcheck output on the original computer. >

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

Here's something that may help. I copied an ancient distribution of Cygwin (simple copy, no installation at all) from another computer, and it seems to work fine on the dual-Xeon. I am attaching the cygcheck output on the original computer. I am a bit skeptical that this will help, because the

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

Quoting Christopher Faylor: > You said you saw the same behavior when running the snapshot. I am > asking you to send the cygcheck and stackdump output from running the > snapshot. Oh! Sure thing. The new output of cygcheck is attached. I have no stackdump to give you, though, because, as I sai

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

On Tue, Feb 24, 2004 at 07:00:36PM +0200, Michael Brand wrote: >>On Tue, Feb 24, 2004 at 01:11:37PM +0200, Michael Brand wrote: >>>I replaced cygwin1.dll with the latest snapshot, and I still get exactly the >>>same behavior(s). >cgf wrote: >>Could you resend (as attachments) the cygcheck output a

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

Quoting Christopher Faylor: > Could you resend (as attachments) the cygcheck output and the stackdump? I'm sorry? I must have misunderstood the request. The cygcheck output was originally sent as an attachment, and is currently available from

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

On Tue, Feb 24, 2004 at 01:11:37PM +0200, Michael Brand wrote: >Quoting Larry Hall <[EMAIL PROTECTED]>: > >> >> This all sounds like problems that have been reported before against >> 1.5.7 >> and have been subsequently fixed and available in snapshots. If you >> have a >> chance, it's worth the

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

Quoting Larry Hall <[EMAIL PROTECTED]>: > > This all sounds like problems that have been reported before against > 1.5.7 > and have been subsequently fixed and available in snapshots. If you > have a > chance, it's worth the small effort to try out a snapshot to see if > all > the problems you'

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

At 11:43 AM 2/23/2004, Michael Brand you wrote: >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 >t

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

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

Re: 1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

On Feb 23 15:02, Michael Brand wrote: > 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/'` Works for me. Did you test this with a recent snapshot from http://cygwin.com/snapshots/ ? Corinna -

1.5.7: Problem with tcsh 6.12.00-7 / sed 4.0.8-1

Hello, I'm a user of cygwin for several years now, and have built many large scripts and applications using it. Lately, in a new installation on new computers, scripts started to get stuck, either becoming idle or stuck in full CPU usage. Importing older versions of the programs from computers