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

subversion/bdb 'invalid argument' errors

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-07-23 19:54:16 CEST

Hey folks,

We're getting a lot of reports of mysterious BerkeleyDB "invalid
argument" errors. They all seem to be coming from people who recently
upgraded to Subversion 1.0.5, 1.0.6, or 1.1.0-rc1. The svn
development team is trying to get to the bottom of this, so we're
mailing the people who have reported this error to the users@ list.
It's been filed as issue 1968, and we want to fix it ASAP
(http://subversion.tigris.org/issues/show_bug.cgi?id=1968).

Many of you get this error just trying to run 'svnadmin create
repos'. If that happens to you, can you follow the instructions at
the bottom of this mail, so that we can get some debugging
information?

If you get the error in some other way (say, running 'svn ls
file:///'), the algorithm only needs to be adjusted slightly. Email
back for help if you have questions.

Thanks for helping!

----------------------------------------

1. Build Subversion however you built it before but add the following
   options to whatever you're passing configure:
   --enable-maintainer-mode --disable-shared

2. Make sure that your APR libraries are stripped (for whatever reason
   what follows below doesn't seem to work right if they aren't).

3. Make a file, call it say gdb.run and put the following in it:

break main
set args create foo
set $_exitcode = -1
run
while $_exitcode < 0
step
end
quit

4. Now from the top of the source tree run:

    gdb subversion/svnadmin/svnadmin -x gdb.run > gdb.out

5. Please post the gdb.out file.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 23 19:57:29 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.