RE: 1.1.8-2 Access violation (sshd)

[Heitzso <xxh1 at cdc dot gov>]

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.

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

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

Heitzso

-----Original Message-----
From: Christopher Faylor [mailto:cgf@redhat.com]
Sent: Saturday, February 03, 2001 12:44 AM
To: cygwin@cygwin.com
Subject: Re: 1.1.8-2 Access violation (sshd)


Does the 2001-Feb-01 cygwin snapshot cause any difference in this behavior?
See http://cygwin.com/ for the link to cygwin snapshots.

cgf

On Thu, Feb 01, 2001 at 04:24:04PM -0000, C wrote:
>Hi there
>
>Hope you can help because this has stumped me. Please find attached
>'cygcheck.out'
>
>File version are (have also tried earlier versions):
>ash    20010129
>bash    2.04-7
>cygwin    1.1.8-2
>openssh    20001221
>
>Problem:
>When using sshd as a service installed with srvany I get the following
>repeating error. On any user account that I create post OS (Win2k) install
I
>get good results when I initiate a ssh session to the host.
>
>However there are 2 user accounts that repeat the following error only
>through an ssh session.
>
>      0 [main] ???a 0 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
>Exception: STATUS_ACCESS_VIOLATION at eip=61001B47
>eax=00000001 ebx=45494C43 ecx=00000000 edx=45494C4B esi=00000000
>edi=0247FF40
>ebp=0247F9FC esp=0247FE98 program=???a
>cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023
>Stack trace:
>Frame     Function  Args
>0247F9FC  61001B47  (00000000, 00000000, 00000000, 00000000)
>0247FEC0  61001B47  (000000D0, 00000001, 0247FF10, 6100326E)
>0247FF10  61003380  (00000000, 00000000, 00000000, 00000000)
>0247FF40  61003A3D  (00401208, 00000000, 82050020, 00000000)
>0247FF60  61003A7C  (00000000, 00000000, 820501B0, 00000005)
>0247FF90  00469C3B  (00401208, FFFFFFFF, 80430C77, 00000000)
>0247FFC0  0040103D  (00000000, 00000000, 7FFDF000, 00000000)
>0247FFF0  77E992A6  (00401000, 00000000, 000000C8, 00000100)
>End of stack trace\[\033]0;\w\007
>\033[32m\]\u@\h \[\033[33m\w\033[0m\]
>
>this specific dump was starting bash from sh.
>
>The user accounts are, Administrator and whatever other account was created
>at the installation of the OS as the admin account to log on as. I have
>checked and double checked the privelidges and attributes of these users
and
>they appear identical to every other.
>
>Some commands do work e.g. 'pwd, cd' produces acpected results 'ls, vi'
>stack dump......
>
>If you would like any more details please feel free to contact me.
>Regards
>CraigT


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

-- 
cgf@cygnus.com                        Red Hat, Inc.
http://sources.redhat.com/            http://www.redhat.com/

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