Re: MinGW port - initial work uploaded

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jan 23, 2007, 19:28 UTC
Message-ID: <Pine.LNX.4.63.0701232025160.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <Pine.LNX.4.63.0701232012440.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Hi,

On Tue, 23 Jan 2007, Johannes Schindelin wrote:

Show 18 quoted lines

> On Tue, 23 Jan 2007, Christian MICHON wrote:
> 
> > On 1/23/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > > maybe I'm stuck with windows at work, but I still use vim inside mingw.
> > > 
> > > I don't:
> > > 
> > > $ vi
> > > m.AllocationBase 0x0, m.BaseAddress 0x715B0000, m.RegionSize 0x4D0000,
> > > m.State 0x10000
> > > C:\msys1\bin\vim.exe: *** Couldn't reserve space for cygwin's heap
> > > (0x715B0000 <0xB10000>) in child, Win32 error 487
> > 
> > interesting. which version of msys are you using ?
> > I'm using this snapshot successfully:
> > msysCORE-1.0.11-2007.01.19-1
> 
> I cannot find that file.

I finally found it. I did not look in "Snapshots", but in "Current" and "Candidate".

And I found the bug: I always extracted with MSYS' own tar in MSYS' own rxvt. Windows is very challenged from time to time, for example when replacing files which are in use, and this led to my bash never being replaced.

Now, Windows executables are not so easily relocated, it seems, and the old bash kept on nicely clashing with the new vim. It sounds horrible, that one program can take away a memory range from another program, just by being not relocatable. And it is.

Ciao, Dscho