Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
X-WM-Posted-At: avacado.atomice.net; Sun, 30 Jun 02 01:08:19 +0100
Message-ID: <010101c21fca$3dbc7150$0100a8c0@advent02>
From: "Chris January" <chris AT atomice DOT net>
To: <cygwin-developers AT cygwin DOT com>
References: <3D1B4043 DOT EF2CA37A AT ieee DOT org> <3D1B4043 DOT EF2CA37A AT ieee DOT org> <3 DOT 0 DOT 5 DOT 32 DOT 20020627224059 DOT 0080d5b0 AT mail DOT attbi DOT com> <20020629031639 DOT GA14536 AT redhat DOT com> <005801c21f59$e116e680$0100a8c0 AT advent02> <20020629172702 DOT GA29746 AT redhat DOT com>
Subject: Re: Slowdown
Date: Sun, 30 Jun 2002 01:08:19 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

> >> >I had a look, but the cvs build fails for me tonight and I can't test.
> >>
> >> Details?
> >Is it the same error as this:
> >http://www.cygwin.com/ml/cygwin/2002-06/msg01681.html ?
>
> Who knows?  You could read the above as implying that Pierre was unable to
> build cygwin at all, too.
>
> I think you can take it as a given that I at least run bash and start a
> few programs before I release a snapshot or check something in.  So,
> cygwin should not be basically broken from my point of view.
I wasn't implying that you hadn't tested it at all. Rather, I was interested
in whether the error I was seeing was unique to me, or whether other people
had seen the same error too (e.g. Pierre). For example, the tty dup error
that I see 50% I start bash is pretty much unique to me due to the way I
have modified cygwin.bat. But other errors may be experienced by more than
one person and those should be given higher priority.

> If this still happens to you after today's checkin, then I'd really
> appreciate if you could track the problem down.
I'm doing so now. I have already provided a full stack backtrace, but I will
attempt to track the error done myself.

Chris