git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: "git-svn fetch" segfaults on unknown user

From
JSJens Seidel <jensseidel@users.sf.net>
Date
Nov 6, 2008, 23:08 UTC
Message-ID
<20081106230804.GA27848@merkur.sol.de>
In-Reply-To
<20081106154808.GA27102@merkur.sol.de>
On Thu, Nov 06, 2008 at 04:48:09PM +0100, Jens Seidel wrote:
Show 12 quoted lines
> On Thu, Nov 06, 2008 at 03:43:18PM +0100, Mikael Magnusson wrote:
> > 2008/11/6 Jens Seidel <jensseidel@users.sf.net>:
> > > I noticed the following bug in git-svn version 1.6.0.3 (svn 1.5.5):
> > >
> > > "git-svn fetch" segfaults
> 
> "gdb -c core" is useless, it just mentions the error occured in
> "perl git-svn fetch" and there is no stacktrace (don't know how to
> debug perl).
> 
> I removed now both [svn] options and it failed again. So it seems a problem
> with file:// access while svn+ssh:// works well.
Could this be possible?

I tried now also to svnsync the same repository on the server which I access with svn+ssh://. "svn-git fetch" fails on this as well, strange ... The hook scripts or the property added by "svnsync init" are not responsible, right?

> > Are you sure this isn't the regular svn 1.5.x crash? Ie, does
> > compiling subversion with --disable-runtime-module-search fix it?
No, it did not help.

I tried to reproduce it with a simple svn repository instead of my larger (not public) one but failed.

What further information do you need? Is there any way to obtain more debug info?
Jens
Previous: Jens Seidel
Message 4 of 4 in “Bug: "git-svn fetch" segfaults on unknown user”
  1. Jens SeidelNov 6, 2008
  2. Mikael MagnussonNov 6, 2008
  3. Jens SeidelNov 6, 2008
  4. Jens SeidelNov 6, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.