From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Fu, Siyuan" <siyuan.fu@intel.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: "git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map
Date: Thu, 24 Mar 2016 13:49:55 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1603241348220.4690@virtualbox> (raw)
In-Reply-To: <B1FF2E9001CE9041BD10B825821D5BC5548BEBDC@shsmsx102.ccr.corp.intel.com>
Hi Siyuan,
On Thu, 24 Mar 2016, Fu, Siyuan wrote:
> I meet below error when using the "git svn" related command, and I tried
> to reinstall the GIT but the issue is still there. Has anybody ever meet
> this and know how to solve it?
>
> GIT version: git version 2.7.4.windows.1
> OS: Windows 8 64bit
>
> $ git svn fetch
> 4 [main] perl 9296 child_info_fork::abort: unable to map C:\Program Files\Git\usr\bin\msys-svn_subr-1-0.dll, Win32 error 1114
> 4 [main] perl 4480 child_info_fork::abort: unable to map C:\Program Files\Git\usr\bin\msys-svn_subr-1-0.dll, Win32 error 1114
> 12 [main] perl 8572 child_info_fork::abort: unable to map C:\Program Files\Git\usr\bin\msys-svn_subr-1-0.dll, Win32 error 1114
The problem has been reported to Git for Windows' bug tracker (twice,
actually):
https://github.com/git-for-windows/git/issues/650
The problem is that it seems to be impossible to reproduce this error
except with *some* setups.
If you can help me to reproduce it, we are a big step closer to resolving
the problem.
Ciao,
Johannes
next prev parent reply other threads:[~2016-03-24 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 2:07 "git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map Fu, Siyuan
2016-03-24 12:49 ` Johannes Schindelin [this message]
2016-03-25 0:53 ` Fu, Siyuan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1603241348220.4690@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=siyuan.fu@intel.com \
/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.
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 NNTP newsgroup(s).