threads / discuss / 41804

"git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map

Subject: "git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map

## tl;dr

3 messages between Mar 24, 2016 and Mar 25, 2016.

replies: 2people: 2as markdown or json

Fu, Siyuan· Mar 24, 2016, 02:07 UTC · lore
Hi, all
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

Best Regards Siyuan

Johannes Schindelin· Mar 24, 2016, 12:49 UTC · re: Fu, Siyuan · lore

Re: "git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map

Hi Siyuan,
On Thu, 24 Mar 2016, Fu, Siyuan wrote:
Show 11 quoted lines
> 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

Fu, Siyuan· Mar 25, 2016, 00:53 UTC · re: Johannes Schindelin · lore

RE: "git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map

Johannes,
I don't have detail steps for the reproduce, but I could share some information.
Yesterday one of my colleagues told me he also met this error after he updated GIT to latest 2.7.4, same with me. Then we uninstall the 64bit GIT and install a 32bit GIT on our 64bit Windows 8 machines, and the new installed 32bit GIT works well.
We are using the TortoiseGit with GIT, beside this I think there are no more special different settings.

Thanks Siyuan

Show 36 quoted lines
> From: Johannes Schindelin [mailto:Johannes.Schindelin@gmx.de] 
> Sent: Thursday, March 24, 2016 8:50 PM
> To: Fu, Siyuan <siyuan.fu@intel.com>
> Cc: git@vger.kernel.org
> Subject: Re: "git svn fetch" error: [main] perl 9296 child_info_fork::abort: unable to map
> 
> 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
>

← back to recent threads