git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heinrich Nirschl" <heinrich.nirschl@gmail.com>
To: "Alex Bennee" <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn crashing perl
Date: Sat, 18 Oct 2008 18:05:44 +0200	[thread overview]
Message-ID: <394ab6ec0810180905t5faca9cbnc7b73267a72deddc@mail.gmail.com> (raw)
In-Reply-To: <b2cdc9f30810180642n22b800ddg244555bf788a83bc@mail.gmail.com>

On Sat, Oct 18, 2008 at 3:42 PM, Alex Bennee <kernel-hacker@bennee.com> wrote:
> Hi,
>
> Doing a git-sv fetch --fetch-all is generating a SEGV in perl while I
> try and update my repo. Although I can look at the backtrace in perl
> it doesn't really tell me much. Any tips on how I can get more info?
>

This seems to be a problem of the subversion perl bindings. See for example:
http://subversion.tigris.org/issues/show_bug.cgi?id=3007

  reply	other threads:[~2008-10-18 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 13:42 git-svn crashing perl Alex Bennee
2008-10-18 16:05 ` Heinrich Nirschl [this message]
2008-10-18 22:00   ` Alex Bennee
2008-10-19  6:39     ` Heinrich Nirschl

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=394ab6ec0810180905t5faca9cbnc7b73267a72deddc@mail.gmail.com \
    --to=heinrich.nirschl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kernel-hacker@bennee.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).