Re: Unexpected pass for t6120-describe.sh on cygwin

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sep 13, 2017, 13:11 UTC
Message-ID: <alpine.DEB.2.21.1.1709131448390.4132@virtualbox>
In-Reply-To: <52f990d5-cdac-b516-269c-acbb68897e6e@grubix.eu>

Hi Michael,

On Wed, 13 Sep 2017, Michael J Gruber wrote:

Show 6 quoted lines

> Could you please try and report on the following (cygwin, MinGW):
> 
> ulimit -s
> ulimit -s 4096 # anything lower than the value from above
> ulimit -s
> bash -c "ulimit -s"

Git Bash (MINGW, well, not precisely [*1*]):

	me@work MINGW64 ~
	$ ulimit -s
	2032

	me@work MINGW64 ~
	$ ulimit -s 4096 # anything lower than the value from above

	me@work MINGW64 ~
	$ ulimit -s
	4096

	me@work MINGW64 ~
	$ bash -c "ulimit -s"
	2032

Judging by your comment, 4096 should be replaced. So here goes again:

	me@work MINGW64 ~
	$ ulimit -s 1024

	me@work MINGW64 ~
	$ ulimit -s
	1024

	me@work MINGW64 ~
	$ bash -c "ulimit -s"
	2032

And here is the same output of my 64-bit Cygwin installation (just updated to the current [*2*] one):

	me@work  ~
	$ ulimit -s
	2032

	me@work  ~
	$ ulimit -s 1024

	me@work  ~
	$ ulimit -s
	1024

	me@work  ~
	$ bash -c "ulimit -s"
	2032

Ciao, Dscho

Footnote *1*: I know it is confusing for Linux folks, there are two very different classes of executables in Git for Windows: MSYS2 ones and MINGW ones. The former implicitly link against the MSYS2 runtime, and therefore can make use of its POSIX emulation layer, the latter do not, and therefore they can use "only" what the Win32 API provides. For details, see https://github.com/git-for-windows/git/wiki/The-difference-between-MINGW-and-MSYS2