git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Uli Heller <uli.heller@daemons-point.com>
To: git@vger.kernel.org
Subject: Re: git svn fetch segfault on exit
Date: Mon, 02 Sep 2013 15:05:50 +0200	[thread overview]
Message-ID: <52248D2E.4090206@daemons-point.com> (raw)
In-Reply-To: <CAPWhs-6E_9T61uf20YKXzwE2j8Tq-sOU9BUw_dVVe=LAH69_iw@mail.gmail.com>

Am 02.09.2013 13:57, schrieb Evgeny Kotkov:
>> Every git svn call that involves a fetch produces a segmentation fault on
>> exit (but the operation succeeds).
>  From what I see, this looks quite similiar to the 'serf' issue I've recently
> reported to the serf-dev mailing list [1].  It should be fixed by now, so,
> the latest serf@trunk build should work fine.
>
> [1]: https://groups.google.com/d/msg/serf-dev/gOn9HTUN98U/pz0_AqdrmJYJ
>
>

I've tried the patch for 'serf' included in the thread mentioned above 
and I can confirm that it fixes the issue for me.
Thanks Evgeny!

Best regards, Uli.

      reply	other threads:[~2013-09-02 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  9:21 git svn fetch segfault on exit Jonathan Lambrechts
2013-07-18 12:18 ` Thomas Rast
2013-09-02  7:40 ` uli
2013-09-02 11:57 ` Evgeny Kotkov
2013-09-02 13:05   ` Uli Heller [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=52248D2E.4090206@daemons-point.com \
    --to=uli.heller@daemons-point.com \
    --cc=git@vger.kernel.org \
    /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).