Mail Archives: cygwin/2001/11/02/17:10:29
Getting ready to restore my system I noticed this file:
--- start of /SSHD.EXE.stackdump
Exception: STATUS_ACCESS_VIOLATION at eip=6102D308
eax=00000000 ebx=6100161B ecx=00000000 edx=00000000 esi=610947B4
edi=00001600
ebp=007EF2B8 esp=007EF2AC program=D:\CYGNUS\USR\SBIN\SSHD.EXE
cs=017F ds=0187 es=0187 fs=492F gs=48EE ss=0187
Stack trace:
Frame Function Args
007EF2B8 6102D308 (007EF426, 007EF2F4, 61059C98, 00000400)
007EF2F8 004355E1 (007EF426, 007EF348, 007EF368, 007EF344)
007EF388 0040D255 (004B573C, 007EF426, 00000016, 6107C708)
007EF3B8 0040D1B3 (004B573C, 007EF426, 00000000, 00000000)
007EF818 0040E109 (004B573C, 00401222, 007EFD68, 00402E71)
007EFD68 00402E84 (00000004, 61112E40, 00A20278, 00000000)
007EFDA8 61003D16 (00000000, 00000000, 00000000, 00000000)
007EFDC8 61003F11 (004027E0, 00000000, 007EFE08, 004A72F3)
007EFDD8 61003F4D (00000000, 00000000, FFFFFFFF, 00000002)
007EFE08 004A72F3 (004027E0, 007EFC8C, BFFC9490, 007EFF68)
007EFE38 0040103D (00000000, 8177138C, 005E0000, 64687353)
007EFF78 BFF8B560 (8176D3B8, 00000008, 8177138C, 00000000)
0 [main] sshd 503177 handle_exceptions: Error while dumping state
(probably corrupted stack)
--- end of file
Based on the time, it is was produced by the 'sshd' command after my first
attempt to use the snapshot (cygwin1.dll replaced by cygwin1-20011101.dll).
Hope this helps,
Kris
-----Original Message-----
From: Kris Huber
Sent: Friday, November 02, 2001 12:28 PM
To: 'David Starks-Browning'
Cc: 'cygwin AT cygwin DOT com'
Subject: RE: ssh error 'The descriptor is a file, not a socket'
Hello David,
This morning I tried the snapshots cygwin1-20011101.dll (moved it to
/bin/cygwin1.dll) and the install stapshot cygwin-20011101.tar.bz2 (unpacked
it so it replaces many files under /usr - /usr/bin seems aliased to /bin
somehow). With both ways of installing the snapshot, sshd gives
segmentation fault (worse than what was happening under the release
version). Actually, I've noticed that outgoing ssh's and ftp's also seg
fault, so the problem is unlikely ssh-related, I think.
I'll restore my cygwin 1.3.3 now and hope someone can make sense of the ssh
debug log I sent earlier.
Also, the download of source I got for openssh
(openssh-2.9.9p2-1-src.tar.bz2) was corrupted (not a bz2 file). I
downloaded from both ftp://planetmirror.com and ftp://ftp.nas.nasa.gov and
got the same corrupted file.
Thanks,
Kris
-----Original Message-----
From: David Starks-Browning [mailto:starksb AT ebi DOT ac DOT uk]
Sent: Thursday, November 01, 2001 5:48 PM
To: Kris Huber
Cc: 'cygwin AT cygwin DOT com'
Subject: ssh error 'The descriptor is a file, not a socket'
On Thursday 1 Nov 01, Kris Huber writes:
> Hello,
>
> I'm trying to use cygwin's sshd to allow my Linux box to log into my win98
> computer using the 'ssh host' command. The authentication goes OK, but
> after 'entering interactive session' I get the following error on the
client
> side:
> 'getpeername failed: The descriptor is a file, not a socket'
>
> I've also seen 'getsockname failed: The descriptor is a file, not a
socket'
> with some variations of the ssh command options.
Try a snapshot, it should be fixed there. (But snapshots may
introduce other problems...)
Cheers,
David
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -