Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <003c01c296d2$83d5a330$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <200211272159 DOT gARLxIX11334 AT mailgate5 DOT cinetic DOT de> <02d501c29665$1b7d3950$78d96f83 AT pomello> <3DE5EBD8 DOT 8080303 AT decodon DOT com>
Subject: Re: Bug in Cygwin SSHD on windows XP
Date: Thu, 28 Nov 2002 11:37:21 -0000
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.2800.1106

Frank-Michael Moser <moser AT decodon DOT com> wrote:

>  > Because vague bug reports are all we have. And no-one can
>  reproduce it > either.
>  >
>
> http://sources.redhat.com/ml/cygwin/2002-07/msg01745.html
>
> When you investigat that thread you do not find only "vague bug
> reports".

I'm sorry, I didn't remember that thread. You did indeed provide pretty much
all the debug information it is possible to provide.

It's a shame that this problem is so elusive.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/