Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Reply-To: Cygwin List <cygwin@cygwin.com>
Message-Id: <6.1.0.6.0.20041021090230.04f9d298@pop.prospeed.net>
X-Sender: 
Date: Thu, 21 Oct 2004 09:03:01 -0400
To: Wayne A McAuliffe <waynemc@au1.ibm.com>, cygwin@cygwin.com
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
Subject: Re: ssh.exe 3.7.1p1:  crashing with STATUS_ACCESS_VIOLATION error  <at>  0x016E65A8
In-Reply-To: <loom.20041021T063104-226@post.gmane.org>
References: <loom.20041019T012057-477@post.gmane.org> <6.1.0.6.0.20041019085857.04434bb8@pop.prospeed.net> <loom.20041020T061045-935@post.gmane.org> <6.1.0.6.0.20041020205359.04bf33e0@pop.prospeed.net> <loom.20041021T063104-226@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 12:35 AM 10/21/2004, you wrote:
>Larry Hall writes:
>
>> Sorry, I don't see it.  If it's truly a problem only when you ssh to one
>> server (and the other 2499 are fine), I'd suggest looking at the differences
>> in configuration and installation on that server compared with one of the 
>> others.  
>> 
>
>Yes, this is the next course of action.
>If I end up fixing the problem I'll post my discoveries here in case anyone
>comes across a similar crash with ssh.exe ...


Cool.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/