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

Re: git svn fetch segfaults

From
DSDennis Schridde <devurandom@gmx.net>
Date
Jan 10, 2008, 01:45 UTC
Message-ID
<200801100245.05647.devurandom@gmx.net>
In-Reply-To
<7v4pdmiwo4.fsf@gitster.siamese.dyndns.org>

Replying to this, as I haven't recieved the newer mail. (Not subscribed.) Handcopied the text, hope I didn't forgot anything.

Show 17 quoted lines
> > > Has anybody determined which executable is the segfaulting one?
> >
> > I just tried to, but it's still running, at r600 now.
> >
> > > If it is svn executable spawned by Perl that runs git-svn, or
> > > libsvn shared object linked to Perl while running git-svn, I
> > > suspect testing with different git versions will not be very
> > > productive.
> >
> > Oh well, anyway, just for the record:
> > doener@atjola:~ $ svn --version
> > svn, version 1.4.4 (r25188)
> >
> > doener@atjola:~ $ git --version
> > git version 1.5.4.rc1.11.gd2f82
>
> It finished by now, no segfault with --use-svnsync-props.

For me it always segfaulted at r13 in tags/1.10a. I crosses r13 before that already (trunk), but doesn't crash there.

I am now recompiling svn,git,perl to create a coredump, will the rerun it and hopefully get some backtraces from the dump.

Btw, I am running perl 5.8.8, in case that matters somehow.
--Dennis
Previous: Björn Steinbrink
Message 7 of 7 in “git svn fetch segfaults”
  1. Dennis SchriddeJan 8, 2008
  2. Miklos VajnaJan 9, 2008
  3. Dennis SchriddeJan 9, 2008
  4. Junio C HamanoJan 9, 2008
  5. Björn SteinbrinkJan 9, 2008
  6. Björn SteinbrinkJan 9, 2008
  7. Dennis SchriddeJan 10, 2008

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.