fatal error on running "man" remotely

[lusitania]

Hi

I'm getting a fatal when calling man on a remote Ubuntu Trusty:

~$ man bash
      0 [main] ssh 9412 C:\Program Files\Git\usr\bin\ssh.exe: *** fatal error - cmalloc would have returned NULL
angup

However, its fine to do the same on an Ubuntu Precise running in a Vagrant box.

Host: Windows 10 x64
Git4Win 2.5.0

[dscho]

Render me absolutely confused. Ubuntu? What does that have to do with Git for Windows? Please clarify. In fact, you really want to volunteer information that allows others to understand the problem. If you expect others to ask for clarification, you will find that most people just don't.

[lusitania]

It is the ssh.exe bundled with Git4Win that raises the error. I connected to a Linux/Ubuntu machine using ssh.exe from within a Git Bash shell (Mingw). I assume the issues does not originate from Git itself rather than MinGW under particular* circumstances. If that is the case you may need to update your dependencies... hopefully the MinGW team is aware of this and you'd just pull in the proper fix.

Best,
L

*) After I reduced my screen buffer from 10k down to 1k lines the error wasn't raised any more.

[dscho]

Unfortunately, this is wrong on at least three accounts:

• there is still no MCVE, despite the fact that it should be possible for you to install Vagrant and test whether it already fails with that. I do expect a little assistance in resolving the bug, after all
• ssh is not a MinGW program. It is an MSys2 program. This may be important, so it is really necessary to be very precise in communicating.
• "hopefully the MinGW team is aware" just cries out loud for some proper investigation rather than hoping.

[lusitania]

Unfortunately I fail to understand what you are trying to tell me. MCVE is an abbreviation unknown to me. And whether ssh is a part of MinGW or MSys2 is not transparent to me. All I am able to see is MinGW's prompt. So there is no way for me to be any more precise than done already. You are the one who has the answers. I can only guess. In the end it is your package that breaks, and again, I can only tell you.

Best

[dscho]

An MCVE is a Minimal, Complete and Verifiable Example. You cannot seriously expect a maintainer of a highly popular software to spend three or more days to chase a bug for you. You really want to make it as easy as possible for others to reproduce your problem. You are asking other to spend time for you, after all. It should be self-evident that you are more likely helped if you respect the time and expertise of those you ask for help.

Now, I gave you a very good hint how to make such an MCVE: by using Vagrant, you essentially install an Ubuntu Virtual Machine into which you can ssh. That is not exactly the intention of Vagrant, but it just happens to be the fastest way for you to set up a reproducible environment.

And just for fun, I did ssh into an Ubuntu Trusty machine I have access to (which you should not have assumed) and I did call man bash and (probably surprising to you, but not me) it worked without a hitch. No problem. Certainly no crash.

Of course, my account would be incomplete without the following information (which BTW should be provided with every bug report, as per our guidelines linked from our Contribute section on our home page):

Git Bash 64-bit on Windows Server 2008 R2, connecting to an Ubuntu Trusty 64-bit machine. Works.

[kumarharsh]

@dscho seems like I'm getting the same errors while using newer builds of Git for Windows which has the bundled ssh:

  1 [main] ssh 5852 C:\bin\Git\usr\bin\ssh.exe: *** fatal error - cmalloc would have returned NULL

1194 [main] ssh 5852 cygwin_exception::open_stackdumpfile: Dumping stack trace to ssh.exe.stackdump

The stackdump mentioned in the dump just has the same text.

This happens usually when I have ssh'd into a server and try to cat or less a large file (not always, but rather frequently).

Try downloading this file and less-ing it: https://1drv.ms/u/s!ArGqE3U0XhYmu5wtGK-qFiiPvUvfdQ

Setup:

ConEmu 180114 Alpha - 64-bit
> git --version
git version 2.16.1.windows.4
> ssh -V
OpenSSH_7.6p1, OpenSSL 1.0.2n  7 Dec 2017

[dscho]

@kumarharsh is ConEmu important here? Or can you reproduce with Git Bash or Git CMD? I ask because I do not want to spend the time setting up ConEmu (which I personally do not prefer) just to reproduce this issue (and I do ssh into a Linux VM all the time, without any of the indicated problems, although I did hit the error message recently when calling vim.exe but the problem went away on its own accord.).

[kumarharsh]

@dscho - yes, it happens with vim too from time to time. As for you, it also goes away for me after some time. I'll try to reproduce it with git bash.

---

Maddeningly enough, the less is now working when I've put the file in the onedrive folder.

[dscho]

Maddeningly enough, the less is now working when I've put the file in the onedrive folder.

Which file?