AW: "unable to remap" error with git svn after upgrade to Win10

AW: "unable to remap" error with git svn after upgrade to Win10

[Christoph Murczek]

Just wanted to let you know: a re-install of git also fixed the problem.

Cheers,
Christoph

-----Ursprüngliche Nachricht-----
Von: Christoph Murczek 
Gesendet: Monday, July 13, 2015 14:10
An: 'git@vger.kernel.org'
Betreff: "unable to remap" error with git svn after upgrade to Win10 

Hi,
I'm using git for windows 1.9.5-preview20150319 and was successfully using git svn, but after upgrading (from Win8.1) to Win10 git svn doesn't work anymore. I get
	C:\Program Files (x86)\Git\bin\perl.exe: *** unable to remap C:\Program Files (x86)\Git\bin\libsvn_repos-1-0.dll to same address as parent -- 0xC30000

I found a couple of issue reports on github referring to a workaround for similar problems using rebase.exe, but are somewhat reluctant to assign memory on a trial and error basis. Can someone give me some pointers on how to deduce a meaningful base address for libsvn_repos-1-0.dll to pass to rebase.exe?

Also with the release date of Win10 approaching you might want to consider a new release addressing the issue. I'd be surprised if I was the only one affected.

Best Regards,
Christoph

Re: AW: "unable to remap" error with git svn after upgrade to Win10

[Johannes Schindelin]

Hi Christoph,

On 2015-07-13 14:24, Christoph Murczek wrote:
> Just wanted to let you know: a re-install of git also fixed the problem.

That is probably because your original report (which I do not quote because that was made too inconvenient by top-posting, sorry) suggests that the culprit was overlapping `.dll` ranges that need to be fixed using the `rebase.exe` tool (which is confusingly completely unrelated to `git rebase`), and that step is part of the installing process.

BTW assuming that you're on a 64-bit setup (Win10 and all...), why do you stick to the 32-bit version of Git for Windows?

Ciao,
Johannes

AW: AW: "unable to remap" error with git svn after upgrade to Win10

[Christoph Murczek]

Hi Johannes,
thanks for explaining why re-installing fixed my problem. Although I still can't wrap my head around why it happened in the first place. It could only be caused by Windows moving the base address of one, but not the other thus causing the overlap. Sounds weird. But then again, what do I know what's going on under the hoods when upgrading to Win10. ;)

In regards to your question: Yes I am running 64bit Windows, but the 32-bit version of git is the only thing I can download. I just double-checked on the webpage, but there's no option to get a 64 bit download link, and if there was some logic determining whether I should get 32 or 64 bit it puts me in the first bucket for some reason.
I haven't considered building from source yet, mostly because the 32bit works fine so far. What would be the benefit? I guess performance when dealing with large repos? If you have a 64bit version available and need feedback let know. Always happy to help out :)

Cheers,
Christoph

-----Ursprüngliche Nachricht-----
Von: Johannes Schindelin [mailto:johannes.schindelin@gmx.de] 
Gesendet: Tuesday, July 14, 2015 10:37
An: Christoph Murczek
Cc: git@vger.kernel.org
Betreff: Re: AW: "unable to remap" error with git svn after upgrade to Win10

Hi Christoph,

On 2015-07-13 14:24, Christoph Murczek wrote:
> Just wanted to let you know: a re-install of git also fixed the problem.

That is probably because your original report (which I do not quote because that was made too inconvenient by top-posting, sorry) suggests that the culprit was overlapping `.dll` ranges that need to be fixed using the `rebase.exe` tool (which is confusingly completely unrelated to `git rebase`), and that step is part of the installing process.

BTW assuming that you're on a 64-bit setup (Win10 and all...), why do you stick to the 32-bit version of Git for Windows?

Ciao,
Johannes

Re: AW: AW: "unable to remap" error with git svn after upgrade to Win10

[Johannes Schindelin]

Hi Christoph,

On 2015-07-14 23:04, Christoph Murczek wrote:

> thanks for explaining why re-installing fixed my problem. Although I
> still can't wrap my head around why it happened in the first place. It
> could only be caused by Windows moving the base address of one, but
> not the other thus causing the overlap. Sounds weird. But then again,
> what do I know what's going on under the hoods when upgrading to
> Win10. ;)

To help that, I just wrote a wiki page about this very problem:

    https://github.com/git-for-windows/git/wiki/32-bit-issues

> In regards to your question: Yes I am running 64bit Windows, but the
> 32-bit version of git is the only thing I can download. I just
> double-checked on the webpage, but there's no option to get a 64 bit
> download link, and if there was some logic determining whether I
> should get 32 or 64 bit it puts me in the first bucket for some
> reason.
> I haven't considered building from source yet, mostly because the
> 32bit works fine so far. What would be the benefit? I guess
> performance when dealing with large repos? If you have a 64bit version
> available and need feedback let know. Always happy to help out :)

So I assumed that you found the official web site of Git for Windows 2.x:

    https://git-for-windows.github.io/

Its download link leads to 32-bit/64-bit versions of the installer and the portable Git.

Ciao,
Johannes