Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <B7F9A3E3FDDDD11185510000F8BDBBF2049E80AE@mcdc-atl-5.cdc.gov>
X-Sybari-Space: 00000000 00000000 00000000
From: Heitzso <xxh1 AT cdc DOT gov>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: RE: 1.1.8-2 Access violation (sshd)
Date: Mon, 5 Feb 2001 13:10:29 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"

Christopher,

There were two of us reporting the register dump.
I managed to sidestep the problem with the user
dir; hence my not downloading the snapshot.  Yes,
I have hesitations with snapshots, not major but 
they can bite (i.e. I walked through all of the Linux
2.4.pre series and trashed my filesystem when
those snapshots had filesystem trashing code in
them).

I just tried to recreate the problem in one
of my environments by dropping the user dir
and logging in and I could not.  Either I
misreported the condition that solved the problem
(the missing user dir) or something was touched
in ssh/ssl mods this past weekend.


Heitzso

-----Original Message-----
From: Christopher Faylor [mailto:cgf AT redhat DOT com]
Sent: Monday, February 05, 2001 12:29 PM
To: 'cygwin AT cygwin DOT com'
Subject: Re: 1.1.8-2 Access violation (sshd)


On Mon, Feb 05, 2001 at 10:42:29AM -0500, Heitzso wrote:
>I believe the stack dump problem goes away (or some forms of it) if the
>user's directory exists.  Also, the garbage at the end is a
>misinterpreted prompt because the passwd entry for the user defaults to
>'sh' which doesn't understand the bash fancy escapes.  Anyway, for me
>the prompt cleaned up by changing my default shell to bash and the
>worst of the register dump by mkdir'ing a '/home/...' directory that
>matched to what was in the passwd file.

Is there some reason why you don't want to try a cygwin snapshot?
I'm not concerned about the prompt.  I'm concerned about the SIGSEGV.

>As noted in an earlier email, cd, pwd and some
>other commands worked, but others, i.e. ls, 
>failed.  

Right.  I don't need a recapitulation of your earlier mail.  I wanted
you to try a newer version of the DLL.

>I just downloaded exp ssh and new ssl and will
>try with those.

Since I don't remember Corinna claiming that she'd solved ay problems
with this release I wouldn't be too hopeful.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple