regards, Uli.
--
View this message in context:
http://git.661346.n2.nabble.com/git-svn-fetch-segfault-on-exit-tp7592205p7595155.html
Sent from the git mailing list archive at Nabble.com.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord
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
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
Hi,
I'm using archlinux with git version 1.8.3.3, svn version 1.8.0
(r1490375) and perl v5.18.0 (built for x86_64-linux-thread-multi)
Every git svn call that involves a fetch produces a segmentation fault
on exit (but the operation succeeds).
*** Error in `/usr/bin/perl': double free or
Jonathan Lambrechts jonathanlambrec...@gmail.com writes:
Every git svn call that involves a fetch produces a segmentation fault
on exit (but the operation succeeds).
*** Error in `/usr/bin/perl': double free or corruption (!prev):
0x02ce1ac0 ***
=== Backtrace: =
5 matches
Mail list logo