Excellent, thanks! Now I just need to wait for a Win32 executable... (I
set up a Linux box for a repository server once, but the hard drive
developed bad sectors in its superblock the day after it was all done --
boo!) Not being 9 time zones away from the server for the next month
and a half would be good too!
From: Max Bowsher [mailto:firstname.lastname@example.org]
Sent: Tuesday, January 11, 2005 17:40
To: email@example.com; Alex R. Mosteo; Kim Sparrow
Subject: Re: Working around presumed svndumpfilter memory leak
Alex R. Mosteo wrote:
> Kim Sparrow wrote:
>> First, a little background: a coworker of mine put half a gig of
>> data into our repository (twice!) and now the repository is about 1.2
>> instead of ~100MB. Doh. This might not be a problem, except that
>> the repository gets a nightly backup to our corporate server, and
>> weeks of backups are kept. You do the math, it's pretty big.
>> So what I want to do is to use svndumpfilter to exclude the offending
>> files, exept it bombs out at the first of the two commits after a
>> minutes, simply saying "abnormal program termination". I found bug
>> which may be the culprit. In this bug report, it's a single large
>> used with 'include'. In my situation it's hundreds of 2-5MB files
>> I want to exclude, while there are other files in the same commit
>> want to keep.
>> Regardless of the source of the problem, does anybody have any
>> suggestions to work around this? I suppose I could manually edit the
>> dumpfile, but I don't relish the thought of removing several hundred
>> large entries from a 1.2 gig dumpfile! I don't even have an editor
>> will handle a file of that size!
> We are on the same boat, but sadly I can't offer any advice. I've been
> suggested to take a build of svndumpfilter with debug symbols and
> posting a gdb backtrace at the point of the abortion. I've been unable
> to do it for various reasons, but if you want to try...
> You can also look for recent posts about svndumpfilter to get the
> specifics of my problem. I would put a pointer but the subversion
> seems to be having problems with tomcat at the moment.
I have fixed this issue 1899. You can either build from trunk, or simply
replace the svndumpfilter/main.c file in 1.1.2 with the one from:
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jan 13 15:50:00 2005