# bug: git-svn seg fault during 'git svn fetch' due to perl < 5.10

2 messages from 2013-01-18 to 2013-01-19. Participants: Durham Goode, Eric Wong.
Thread: https://gitlist.dev/t/32661

## Durham Goode, 2013-01-18 04:14

Subject: bug: git-svn seg fault during 'git svn fetch' due to perl < 5.10
Message-ID: <2B10A89294DA6740AC6155F56842F9CE05234E6C@PRN-MBX01-2.TheFacebook.com>
URL: https://gitlist.dev/e/2B10A89294DA6740AC6155F56842F9CE05234E6C%40PRN-MBX01-2.TheFacebook.com

```
In git 1.8.1, when we do 'git svn fetch' on a large repo, we're seeing a
seg fault.  It's caused by git-svn trying to parse a large yaml file
(introduced in 
https://github.com/git/git/commit/68f532f4ba888f277637a94b4a49136054df0540
) which encounters a perl regex stack overflow bug that was present in
perl < 5.10 (https://bugzilla.redhat.com/show_bug.cgi?id=192400).

We'll find a work around, but it'd be nice if there was a config setting
to let us choose not to use the yaml format.

Let me know if there's a better place to report this.

-Durham

```

## Eric Wong, 2013-01-19 11:51

Subject: Re: bug: git-svn seg fault during 'git svn fetch' due to perl < 5.10
Message-ID: <20130119115101.GA2559@dcvr.yhbt.net>
URL: https://gitlist.dev/e/20130119115101.GA2559%40dcvr.yhbt.net
In-Reply-To: <2B10A89294DA6740AC6155F56842F9CE05234E6C@PRN-MBX01-2.TheFacebook.com>

```
Durham Goode <durham@fb.com> wrote:
> In git 1.8.1, when we do 'git svn fetch' on a large repo, we're seeing a
> seg fault.  It's caused by git-svn trying to parse a large yaml file
> (introduced in 
> https://github.com/git/git/commit/68f532f4ba888f277637a94b4a49136054df0540
> ) which encounters a perl regex stack overflow bug that was present in
> perl < 5.10 (https://bugzilla.redhat.com/show_bug.cgi?id=192400).
> 
> We'll find a work around, but it'd be nice if there was a config setting
> to let us choose not to use the yaml format.

Maybe try a libyaml-based YAML module?  I'm not too familiar
with YAML parsers in the Perl world.  Hopefully Jonathan can help.

> Let me know if there's a better place to report this.

Yes, feel free to Cc: folks who signed-off/acked the change which
introduced the problem for you.

```