[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnsync funniness with bdb repositories

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Thu, 17 Jan 2008 11:18:29 +0100

Hyrum K. Wright wrote:
> Hyrum K. Wright wrote:
..
>
> More weirdness with svnsync. In trying to sync the gcc repository, I get
> consistent segfaults using a trunk build of svnsync. This is a transcript of
> the session:
> $ ~/dev/svn-trunk/subversion/svnsync/svnsync sync \
> file:///home/hwright/test/gcc.bdb
> Copied properties for revision 8132.
> Transmitting file data
> Committed revision 8133.
> Segmentation fault (core dumped)
> $ svnd pd --revprop -r 0 svn:sync-lock file:///home/hwright/test/gcc.bdb
> property 'svn:sync-lock' deleted from repository revision 0
> $ ~/dev/svn-trunk/subversion/svnsync/svnsync sync \
> file:///home/hwright/test/gcc.bdb
> Copied properties for revision 8133.
> Transmitting file data
> Committed revision 8134.
> Segmentation fault (core dumped)
> $ svnd pd --revprop -r 0 svn:sync-lock file:///home/hwright/test/gcc.bdb
> property 'svn:sync-lock' deleted from repository revision 0
> $ ~/dev/svn-trunk/subversion/svnsync/svnsync sync \
> file:///home/hwright/test/gcc.bdb
> Copied properties for revision 8134.
> Transmitting file data
> Committed revision 8135.
> Segmentation fault (core dumped)
>
> It gets through one revision, and then crashes. It doesn't crash on *every*
> revision, but for this repository in this case it is behaving that way. This is
> a transcript of a gdb session.
>
> (gdb) r
> [Thread debugging using libthread_db enabled]
> [New Thread -1216358736 (LWP 30619)]
> Copied properties for revision 8138.
> Transmitting file data
> Committed revision 8139.
>
..

Do you have the same issue with fsfs? I starting syncing the gcc
repository over svn to a local fsfs repository, but the first 100
revisions or so sync without problem.

I don't see anything special about the revisions, besides the fact that
the svn:author revprop isn't set, but that shouldn't be a problem.
Seeing that after you restart svnsync it manages to correctly copy the
revision properties I assume it's a local bug in the new svnsync
callback code.

Can you successfully run the svnsync tests over svn with a bdb repository?

>
> This is the point that I get lost, not having any experience with svnsync.
> Could somebody with more knowledge take a look? Would it be better filed as an
> issue in the the bug tracker?
>
The faulty code was all rewritten on trunk, still, better to create an
issue for 1.5 so we don't forget. I'll have a look once I have more time
(this weekend at the latest). I tried to get a bdb build on my ubuntu
laptop, but that seemed to be a problem (keeps complaining apr-util
isn't linked with bdb).

Lieven

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-17 11:24:20 CET

This is an archived mail posted to the Subversion Dev mailing list.