Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 10 May 2001 23:24:27 -0700 (PDT)
From: Matt <matt AT use DOT net>
X-Sender:  <matt AT cesium DOT clock DOT org>
To: <cygwin-developers AT cygwin DOT com>
Subject: Re: Fix for ssh problems
In-Reply-To: <20010504224503.A20310@redhat.com>
Message-ID: <Pine.NEB.4.30.0105102303590.18125-100000@cesium.clock.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 4 May 2001, Christopher Faylor wrote:

> Corinna reported a problem with sshd and debugged it enough that I
> could (eventually) figure out what I think was happening.  I just
> checked in a fix for the problem, I hope.
>
> I don't know if this will fix Matt's ssh problems or not, but please
> give the current CVS Cygwin a try.

I just tried the 20010508 snapshot, which doesn't fix th problem on win9x.
(The problem being that after scp'ing a file, an ssh process hangs
around.)

As suggested before, I updated my gdb (to 20010428-1) and attempted to
attach to the ssh process. I got the same results as before: gdb misprints
the pid as a negative number, then uses 85% of the CPU. When I try to kill
gdb by closing the window, my machine becomes unresponsive (no capslock
or ctrl+alt+del reponse) for awhile, and
I've found it easier to reboot than wait for it to come back.

Not sure what to do from here. Suggestions? Can someone else try attaching
to the process on win9x and seeing if gdb has the same result?


--
http://www.clock.org/~matt