From: Eric Wong <normalperson@yhbt.net>
To: Steven Grimm <koreth@midwinter.com>
Cc: git@vger.kernel.org
Subject: Re: Segmentation fault in git-svn
Date: Tue, 17 Apr 2007 02:37:43 -0700 [thread overview]
Message-ID: <20070417093743.GA9222@muzzle> (raw)
In-Reply-To: <4623F613.5010108@midwinter.com>
Steven Grimm <koreth@midwinter.com> wrote:
> I expect this is really a libsvn bug, but git-svn triggers it, so I'm
> hoping someone else has run into and solved it, or at least that someone
> can reproduce it.
I've also been working with another user off-list the past few
days on tracking down on a segmentation fault in git-svn.
> If I try to clone the "memcached" public repository with the command line
>
> git-svn clone --branches=branches --trunk=trunk
> http://code.sixapart.com/svn/memcached
I just ran this several (6?) times got a segmentation fault once
with Junio's master @ f948792990f82a35bf0c98510e7511ef8acb9cd3.
Trying it again with the same file that segfaulted earlier, it was
successful, spooky...
I also tried some other patches (see replies) which I've been testing to
fix the other user's problem.
> it cranks along fine until revision 299, then dies with SIGSEGV. If I
> run it again, it appears to pick up where it left off, then dies again
> at revision 399, then again at revision 499. (There are fewer than 600
> revisions in that repo so it's anyone's guess if it'd die at 599 given
> the chance.)
I have definitely not seen this pattern before.
However, the following clone has been problematic at times
git svn clone svn://svn.debian.org/svn/pkg-glibc/glibc-package \
-T trunk -b branches -t tags
> This happens on both a Linux box (amd64, FC4, svn version 1.4.3) and my
> Mac (Intel OS 10.4, svn version 1.2.3 from Fink), so at the very least
> it's not platform-specific. It also happens periodically on the private
> svn repository at my company, though not as predictably. On my Mac, I'm
> using the very latest git code from "master".
I'm running x86, Debian Etch, SVN 1.4.2 from Debian Etch or
1.4.3 from Debian experimental + do_switch patch[1]
Thanks for the stack trace. This is segfaulting at
a different place (expected, being an http:// repo while
the other is svn://)
[1] - http://svn.haxx.se/dev/archive-2007-01/0936.shtml
--
Eric Wong
next prev parent reply other threads:[~2007-04-17 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 22:17 Segmentation fault in git-svn Steven Grimm
2007-04-17 9:37 ` Eric Wong [this message]
2007-04-17 9:40 ` [PATCH (WIP)] git-svn: cache SVN::Ra functions in a more Perl GC-friendly way Eric Wong
2007-04-24 0:50 ` Steven Grimm
2007-04-25 6:40 ` Eric Wong
2007-04-17 9:55 ` Segmentation fault in git-svn Eric Wong
2007-04-18 9:01 ` Eric Wong
2007-04-19 21:31 ` [RFH] " Eric Wong
2007-05-03 12:35 ` Peter Baumann
2007-05-13 8:21 ` Eric Wong
2007-05-13 22:04 ` Steven Grimm
2007-05-14 9:02 ` Peter Baumann
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=20070417093743.GA9222@muzzle \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.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).