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

Re: FSFS Issue...

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2005-12-04 23:32:46 CET

On Fri, Dec 02, 2005 at 05:39:31PM +0000, Malcolm Rowe wrote:
> I've looked at pool management, and I can't see anything wrong in
> that area. I've not yet run valgrind over it though, so I could have
> easily missed something. (Could someone point me towards instructions
> for enabling pool debugging please?)

FWIW, I just finished running 'make check' (ra_local/FSFS only) on
Subversion 1.2.1 with an in-tree APR 0.9.5 and Neon 0.24.7, all via
valgrind. (That is, I replaced 'svn' with a script that wrapped the
real svn executable with valgrind/memcheck. svnadmin was left unwrapped.)

I found nothing significant -- after almost 3,000 runs of 'svn', I only
hit a couple of one-time glibc memory leaks from gettext, setlocale,
getpwent and the like, and an unexpected SIGSEGV that I couldn't
reproduce. I didn't find any uninitialised reads, use-of-freed-memory,
or anything like that.

Now the fact that I didn't find _anything_ was a bit suspicious, but
I've double-checked what I did, and it seems correct (I configured
at the top level with --enable-maintainer-mode --enable-pool-debug=1;
APR_POOL_DEBUG=1 was defined for all the source files).

So perhaps not a memory corruption problem, or, rather, not one that
'make check' will trigger?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Dec 4 23:33:22 2005

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.