Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 5 Feb 2001 12:29:25 -0500 From: Christopher Faylor To: "'cygwin@cygwin.com'" Subject: Re: 1.1.8-2 Access violation (sshd) Message-ID: <20010205122925.A32710@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: "'cygwin@cygwin.com'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from xxh1@cdc.gov on Mon, Feb 05, 2001 at 10:42:29AM -0500 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