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

Re: [PATCH] More tests for the svn.wc Python bindings

From: Madan U Sreenivasan <madan_at_collab.net>
Date: 2006-06-16 07:46:11 CEST

On Fri, 16 Jun 2006 08:05:49 +0530, David James <djames@collab.net> wrote:

>> Madan U Sreenivasan wrote:
>> ---------------------8<---------------------------------8<------------------
>> > madan@madan ~/wc/trunk $ gdb --args python2.4
>> > ./subversion/bindings/swig/python/tests/wc.py
>> > #0 0x4048180e in apr_palloc () from /usr/lib/libapr-0.so.0
>> > #1 0x4066f8dc in create_svn_repos_t (path=0x403ef3c4
>> > "/tmp/trac-svnrepos", pool=0x0) at repos.c:1540
>> > #2 0x4066fc00 in svn_repos_create (repos_p=0x0, path=0x403ef3c4
>> > "/tmp/trac-svnrepos", unused_1=0x402b90ac "",
>> > unused_2=0x402b90ac "", config=0x0, fs_config=0x0, pool=0x0) at
>> > repos.c:1664
>> > #3 0x408f368a in ?? () from
>> > /usr/lib/python2.4/site-packages/libsvn/_repos.so
> Oops. You're using an old version of the Python bindings with a new
> version of Subversion. I can tell this from the stack trace because
> your Subversion build has debug symbols but your Python bindings build
> does not. Also, I can see that you're running Python bindings from
> '/usr/lib', and it is unusual to keep your trunk bindings in
> '/usr/lib'.

yeah... I just noticed... how come? lemme check... thanks for pointing
out, Garrett..

> Madan, have you tried running the regular 'make check-swig-py' target?
> This target automatically sets up your Python path so that the tests
> will run with the version of the Python bindings in your build tree.
> You may also need to run 'make clean-swig && ./configure' if you want
> to get a completely clean build.

Will do this...

>> > I will try with my laptop at office today... looking at the bt, I
>> > suspect linkages with older versions of libapr... what do you think?
>> I'm not sure - if pool=NULL is a valid argument to create_svn_repos_t(),
>> then at least the Python bindings are not to blame. This must've been
>> broken longer though - this is code that's being called from the trac
>> test cases.
> pool=NULL is not a valid argument to create_svn_repos_t or
> svn_repos_create.

Is it? svn.repos.create() complains that it needs 5 parameters as input,
when I give less than that. I cant figure out which five... Also, there is
no apr_pool_create() function in svn.core (pool related functions are
documented as deprecated)... so how do we create a pool to be passed to


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 16 07:15:54 2006

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