git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christoph Murczek <Christoph.Murczek@iteratec.at>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: AW: "unable to remap" error with git svn after upgrade to Win10
Date: Mon, 13 Jul 2015 12:24:00 +0000	[thread overview]
Message-ID: <8e6220ba0ffb43dbbc7c4eaefd2ab753@CIPEXMB03N1.ci04.de> (raw)

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

             reply	other threads:[~2015-07-13 12:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 12:24 Christoph Murczek [this message]
2015-07-14  8:37 ` AW: "unable to remap" error with git svn after upgrade to Win10 Johannes Schindelin
2015-07-14 21:04   ` AW: " Christoph Murczek
2015-07-15 10:50     ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8e6220ba0ffb43dbbc7c4eaefd2ab753@CIPEXMB03N1.ci04.de \
    --to=christoph.murczek@iteratec.at \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).