From: Dennis Schridde <devurandom@gmx.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>, git@vger.kernel.org
Subject: Re: git svn fetch segfaults
Date: Thu, 10 Jan 2008 02:45:01 +0100 [thread overview]
Message-ID: <200801100245.05647.devurandom@gmx.net> (raw)
In-Reply-To: <7v4pdmiwo4.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Replying to this, as I haven't recieved the newer mail. (Not subscribed.)
Handcopied the text, hope I didn't forgot anything.
> > > 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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-01-10 1:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 22:25 git svn fetch segfaults Dennis Schridde
2008-01-09 0:33 ` Miklos Vajna
2008-01-09 12:53 ` Dennis Schridde
2008-01-09 20:14 ` Junio C Hamano
2008-01-09 20:53 ` Björn Steinbrink
2008-01-09 22:15 ` Björn Steinbrink
2008-01-10 1:45 ` Dennis Schridde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801100245.05647.devurandom@gmx.net \
--to=devurandom@gmx.net \
--cc=B.Steinbrink@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).