ssh.exe and related executables always crash

308 views
Skip to first unread message

A.J. Miberg

unread,
Dec 27, 2011, 3:23:53 AM12/27/11
to msy...@googlegroups.com
Using git version 1.7.6.msysgit.0, ssh.exe and ssh-keygen.exe always crash. This happens immediately; there is no network delay. It happens even when I disable my antivirus.

ssh.exe Application Error The instruction at "0x6805b903" referenced memory at "0x00000000". The memory could not be "read." See attachment.

Reverting to git 1.5.4 solves this, but ssh-keygen is missing so I cannot use it. Other versions of git 1.6.X and 1.7.X similarly fail.

I found some similar but not identical posts: 12 


sshcrash.png

Paul Betts

unread,
Dec 27, 2011, 10:04:54 AM12/27/11
to msy...@googlegroups.com, msy...@googlegroups.com
Can you do the following?

1. Download the debugging tools for windows
2. Run ssh.exe and get it to that crash dialog
3. Open WinDbg, Attach to Process
4. Type command ".dump /ma C:\[Path to your desktop folder]\SshCrash.dmp
5. Zip up that file and upload it somewhere so people on this list can get to it

-- 
Paul Betts

SENT FROM MY COMMODORE 64: RESPONSES MAY BE IN ALL CAPS
<sshcrash.png>

Philip Oakley

unread,
Dec 28, 2011, 2:42:55 PM12/28/11
to msy...@googlegroups.com
In msysgit, how do I get the mtime of a file in a format compatible with the
"git commit --date=<date/time>" format?

I'm looking to use this in a script that imports old zip files to build a
repo and I'd like to fixup the commit date to be that of the last
non-ignored, added/modified file in the exported zip file. I can identify
the most recent file (e.g.)
$ git status -u --porcelain | sed -e "s/^...//" | xargs ls -t -c1 | head -1

But then doing a "ls -l --full-time <file>" produces a different format to
that shown in the git commit documentation e.g. "Wed Dec 28 16:30:27 2011".
The minimal system (msys) it doesn't appear have stat() etc.

Any suggestions for a suitable command?

I'm using a git bash window Git (version 1.7.8-preview20111206).

Johannes Sixt

unread,
Dec 28, 2011, 3:09:41 PM12/28/11
to Philip Oakley, msy...@googlegroups.com
Am 28.12.2011 20:42, schrieb Philip Oakley:
> In msysgit, how do I get the mtime of a file in a format compatible with
> the "git commit --date=<date/time>" format?

On Linux, I can use: stat --format=%Z the-file
I think we have GNU stat in msysgit, so it might work as well.

-- Hannes

Philip Oakley

unread,
Dec 28, 2011, 3:23:52 PM12/28/11
to Johannes Sixt, msy...@googlegroups.com
From: "Johannes Sixt" <j...@kdbg.org> : Wednesday, December 28, 2011 8:09 PM

Unfortunately stat looks to be not present in msysgit.

I got, for my example file.
Philip@PHILIPOAKLEY /d/MatlabPatchTestRepo (master)
$ stat --format=%Z ListTime.txt
sh.exe": stat: command not found

Pat Thoyts

unread,
Dec 28, 2011, 5:34:45 PM12/28/11
to Philip Oakley, Johannes Sixt, msy...@googlegroups.com

Use the 'date' command with the --reference option to take the time
from the referenced file. eg:

pat@FROG ~
$ date --reference=/c/opt/bin/putty.exe
Tue Nov 3 15:20:56 GMTST 2009

pat@FROG ~
$ date --reference=/c/opt/bin/putty.exe +"%s"
1257261656

pat@FROG ~
$ date --reference=/c/opt/bin/putty.exe +"%Y%m%d %H:%M:%S"
20091103 15:20:56

Lots of output options for you to try.

Philip Oakley

unread,
Dec 28, 2011, 7:10:02 PM12/28/11
to Pat Thoyts, Johannes Sixt, msy...@googlegroups.com
From: "Pat Thoyts" <patt...@gmail.com>: Wednesday, December 28, 2011 10:34
PM

> Use the 'date' command with the --reference option to take the time
> from the referenced file. eg:
>
> pat@FROG ~
> $ date --reference=/c/opt/bin/putty.exe +"%Y%m%d %H:%M:%S"
> 20091103 15:20:56
>
> Lots of output options for you to try.
>
That works fine. Many thanks.
Philip

dig...@gmail.com

unread,
Apr 24, 2014, 6:41:40 PM4/24/14
to msy...@googlegroups.com
Here we are in late April 2014, at version 1.9.0.msysgit.0 of git.  And the same issue exists, even the same address.  Was this issue ever resolved?

Johannes Schindelin

unread,
Apr 25, 2014, 8:39:48 AM4/25/14
to dig...@gmail.com, msy...@googlegroups.com
On Thu, 24 Apr 2014, dig...@gmail.com wrote:

> Here we are in late April 2014, at version 1.9.0.msysgit.0 of git. And
> the same issue exists, even the same address. Was this issue ever
> resolved?

Did you work on it?

Richard Tenney

unread,
Apr 25, 2014, 10:54:52 AM4/25/14
to Johannes Schindelin, dig...@gmail.com, msy...@googlegroups.com
No. That's way beyond my involvement level with
git. I'm just starting out and encountered this
exact problem. I was hoping that two years and
several versions later, the problem had been
fixed or had a work-around less drastic than
reverting to git 1.5.4. Something like "get ssh
and its family from xxx and substitute those
programs for the ones that came with git's bash."

I have two versions of SSH that I use regularly
without problems -- PuTTY and the free SSH Secure
Shell Client 3.2.9, both easily downloaded from
various places on the internet. How would I get git bash to use one of them?

Tschüß,
Richard

Johannes Schindelin

unread,
Apr 25, 2014, 11:15:54 AM4/25/14
to Richard Tenney, dig...@gmail.com, msy...@googlegroups.com
Hi Richard,

On Fri, 25 Apr 2014, Richard Tenney wrote:

> At 08:39 AM 4/25/2014, Johannes Schindelin wrote:
> >On Thu, 24 Apr 2014, dig...@gmail.com wrote:
> >
> > > Here we are in late April 2014, at version 1.9.0.msysgit.0 of git. And
> > > the same issue exists, even the same address. Was this issue ever
> > > resolved?
> >
> >Did you work on it?
>
> No. That's way beyond my involvement level with git.

Now you surely understand that pretty much everybody else who experienced
the same issue as you did thought exactly the same: let somebody else fix
it.

That is the state of the issue and it will be, for all the foreseeable
future.

Sorry,
Johannes

Thomas Braun

unread,
May 8, 2014, 4:43:08 PM5/8/14
to msy...@googlegroups.com, dig...@gmail.com
Am 25.04.2014 00:41, schrieb dig...@gmail.com:
> Here we are in late April 2014, at version 1.9.0.msysgit.0 of git. And
> the same issue exists, even the same address. Was this issue ever resolved?
>
> On Tuesday, December 27, 2011 3:23:53 AM UTC-5, A.J. Miberg wrote:
>
> Using git version 1.7.6.msysgit.0, ssh.exe and ssh-keygen.exe
> /always/ crash. This happens immediately; there is no network delay.
> It happens even when I disable my antivirus.
>
> /ssh.exe Application Error The instruction at "0x6805b903"
> referenced memory at "0x00000000". The memory could not be
> "read." /See attachment.
>
> Reverting to git 1.5.4 solves this, but ssh-keygen is missing so I
> cannot use it. Other versions of git 1.6.X and 1.7.X similarly fail.
>
> I found some similar but not identical posts: 1
> <http://code.google.com/p/msysgit/issues/detail?id=227>, 2
> <https://groups.google.com/forum/#%21searchin/msysgit/ssh.exe/msysgit/jW24vV2E-ls/Kd9pPulnR7QJ>

As always if the the problem can not be reproduced on a developers
machine, the chances get slim.

Does for example "ssh -v" also crash? Or does "openssl.exe version" crash?

And /bin/ssh.exe was last changed in 2008, so I would also not expect
that the problem lies in ssh.exe.

Richard Tenney

unread,
May 8, 2014, 11:11:08 PM5/8/14
to Thomas Braun, msy...@googlegroups.com, dig...@gmail.com
Thanks for taking the time to reply to my
query. As my interest in Git is as a tool, its
woes are way at the bottom of my other concerns,
so I have moved on. I am successfully using Git
via TortoiseGit and dropbox. I haven't spent
more time working with msysgit nor on its ssh issue. Sorry.
Tschüß,
Richard

pierre....@gmail.com

unread,
Aug 1, 2014, 9:45:27 AM8/1/14
to msy...@googlegroups.com, thomas...@virtuell-zuhause.de, dig...@gmail.com, r...@digitry.com
Hi there,

I had the same problem and solved it by removing the driver of a webcam (Logitech Quick Cam). Don't ask me why this worked...

- Pierre

Thomas Braun

unread,
Aug 1, 2014, 10:29:14 AM8/1/14
to pierre....@gmail.com, msy...@googlegroups.com, dig...@gmail.com, r...@digitry.com
Am 01.08.2014 um 15:45 schrieb pierre....@gmail.com:
> Hi there,
>
> I had the same problem and solved it by removing the driver of a webcam
> (Logitech Quick Cam). Don't ask me why this worked...
>
> - Pierre

Which also verfifies what is written in the release notes [1].

[1]:
https://github.com/msysgit/msysgit/blob/master/share/WinGit/ReleaseNotes.rtf

Reply all
Reply to author
Forward
0 new messages