Jonathan Lambrechts <> writes:

> Every git svn call that involves a fetch produces a segmentation fault
> on exit (but the operation succeeds).
> *** Error in `/usr/bin/perl': double free or corruption (!prev):
> 0x0000000002ce1ac0 ***
> ======= Backtrace: =========
> /usr/lib/[0x7fd4d83798ae]
> /usr/lib/[0x7fd4d837a587]
> /usr/lib/[0x7fd4d568e9ad]
> /usr/lib/[0x7fd4d568f590]
> /usr/lib/perl5/vendor_perl/auto/SVN/_Core/[0x7fd4d6886920]
> /usr/lib/perl5/core_perl/CORE/[0x7fd4d876f821]
> /usr/lib/perl5/core_perl/CORE/[0x7fd4d8767e26]
> /usr/lib/perl5/core_perl/CORE/[0x7fd4d86f93b0]
> /usr/lib/perl5/core_perl/CORE/[0x7fd4d86fb477]
> /usr/lib/perl5/core_perl/CORE/[0x7fd4d86fca91]
> /usr/bin/perl(main+0x111)[0x400e01]
> /usr/lib/[0x7fd4d8322a15]
> /usr/bin/perl[0x400e71]

Can you check if your version of the perl subversion bindings were
compiled against the perl and subversion versions that you have

Perl -- as an interpreted language -- is mostly supposed to be safe from
such segfaults, and since git-svn is pure perl, the likely culprit is in
the bindings or the svn libraries.  And the easiest way to get that to
break is a version mismatch.

Thomas Rast
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to