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

Re: MAC OSX stack trace, please, for commit-tests.py 59

From: Philip Martin <philip_at_codematters.co.uk>
Date: Fri, 17 Jul 2009 12:53:56 +0100

Philip Martin <philip_at_codematters.co.uk> writes:

> Stefan Sperling <stsp_at_elego.de> writes:
>
>> can you run the same for merge_test 56 (or show me how you run svn
>> tests in valgrind)? I suspect that test may have similar problems.
>
> The way I do it is to manually edit the subversion/svn/svn libtool
> script after the build:
>
> --- svn.orig 2009-07-17 12:10:25.000000000 +0100
> +++ svn 2009-07-17 10:42:44.000000000 +0100
> @@ -133,7 +133,7 @@
> if test "$libtool_execute_magic" != "%%%MAGIC variable%%%"; then
> # Run the actual program with our arguments.
>
> - exec "$progdir/$program" ${1+"$@"}
> + exec valgrind -q "$progdir/$program" ${1+"$@"}
>
> $ECHO "$0: cannot exec $program $*" 1>&2
> exit 1
>
> Then you run the regression tests as normal.

You probably need to enable apr's pool debugging to get the most out
of valgrind. Configure Subversion with CFLAGS=-DAPR_POOL_DEBUG, maybe
build apr and apr-util with --enable-pool-debug as well.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2372037
Received on 2009-07-17 13:54:49 CEST

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