This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ssh.exe 3.7.1p1: crashing with STATUS_ACCESS_VIOLATION error <at> 0x016E65A8
At 12:33 AM 10/20/2004, you wrote:
>Larry Hall writes:
>
>> <snip>
>>
>> Did you try the latest version of OpenSSH and Cygwin?
>
>I upgraded to the following binaries and tried it again,
>
>ssh.exe 3.9p1
>cygcrypto-0.9.7.dll 0.9.7d
>cygwin1.dll 1.5.11
>cygminires.dll 0.98
>cygz.dll 1.2.2
>
>Ugh. Same problem, though obviously a different address (0x16D65A8).
>The strace looks a little different leading up to the crash-
>site though, 3 lines immediately before the exception. No mention of the
>wsock_event this time, and new 'lock / 'unlock lines. Though I guess this
>doesn't help.
>
> 569 2308580 [main] ssh 1285 __cygwin_lock_lock: threadcount 1. not locking
> 505 2309085 [main] ssh 1285 __cygwin_lock_unlock: threadcount 1. not
>unlocking
> 474 2309559 [main] ssh 1285 writev: writev (3, 0x22EB90, 1)
> 1432 2310991 [main] ssh 1285 handle_exceptions: In cygwin_except_handler exc
>0xC0000005 at 0x16D65A8 sp 0x22EA1C
> 1559 2312550 [main] ssh 1285 handle_exceptions: In cygwin_except_handler sig
>11 at 0x16D65A8
>
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.
--
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/