git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git svn fetch segfault on exit

From
Thomas Rast <trast@inf.ethz.ch>
Date
Jul 18, 2013, 12:18 UTC
Message-ID
<878v146ozb.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<51E7B382.8050302@gmail.com>
Jonathan Lambrechts <jonathanlambrechts@gmail.com> writes:
Show 19 quoted lines
> 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/libc.so.6(+0x788ae)[0x7fd4d83798ae]
> /usr/lib/libc.so.6(+0x79587)[0x7fd4d837a587]
> /usr/lib/libapr-1.so.0(apr_allocator_destroy+0x1d)[0x7fd4d568e9ad]
> /usr/lib/libapr-1.so.0(apr_pool_terminate+0x30)[0x7fd4d568f590]
> /usr/lib/perl5/vendor_perl/auto/SVN/_Core/_Core.so(_wrap_apr_terminate+0x50)[0x7fd4d6886920]
> /usr/lib/perl5/core_perl/CORE/libperl.so(Perl_pp_entersub+0x571)[0x7fd4d876f821]
> /usr/lib/perl5/core_perl/CORE/libperl.so(Perl_runops_standard+0x16)[0x7fd4d8767e26]
> /usr/lib/perl5/core_perl/CORE/libperl.so(Perl_call_sv+0x3b0)[0x7fd4d86f93b0]
> /usr/lib/perl5/core_perl/CORE/libperl.so(Perl_call_list+0x2c7)[0x7fd4d86fb477]
> /usr/lib/perl5/core_perl/CORE/libperl.so(perl_destruct+0x1321)[0x7fd4d86fca91]
> /usr/bin/perl(main+0x111)[0x400e01]
> /usr/lib/libc.so.6(__libc_start_main+0xf5)[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 installed?

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
trast@{inf,student}.ethz.ch
Previous: Jonathan LambrechtsNext: uli
Message 2 of 5 in “git svn fetch segfault on exit”
  1. Jonathan LambrechtsJul 18, 2013
  2. Thomas RastJul 18, 2013
  3. uliSep 2, 2013
  4. Evgeny KotkovSep 2, 2013
  5. Uli HellerSep 2, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.