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

Re: Weirdness while testing 1.4.0-rc2 (svnserve processes that don't die)

From: Branko ─îibej <brane_at_xbc.nu>
Date: 2006-07-17 20:21:07 CEST

Philip Martin wrote:
> "Garrett Rooney" <rooneg@electricjellyfish.net> writes:
>
>
>> I'm not seeing the problem here, although my test environment is
>> running on FreeBSD, not Linux, so maybe that's it? Has anyone else
>> run the svnserve tests on bdb 4.4?
>>
>> If you attach to the svnserve processes in gdb what are they doing?
>>
>
> Using trunk on Linux with APR_POOL_DEBUG:
>
> $ svnadmin create repo --fs-type bdb
> $ valgrind -q svnserve -Xr.
> $ svn ls svn://localhost/repo
>
> valgrind shows svnserve failing:
>
[...]
> ==2314== Address 0x446C820 is 16 bytes inside a block of size 28 free'd
>
[...]
> ==2314== Address 0x446C530 is 32 bytes inside a block of size 40 free'd
>
[...]
> ==2314== Address 0x41414141 is not stack'd, malloc'd or (recently) free'd
> ==2314==
> ==2314== Process terminating with default action of signal 11 (SIGSEGV)
> ==2314== Access not within mapped region at address 0x41414141
>
[...]

Oh bother. I must have been smoking something really weird to not notice
the this would obviously happen.

Back to the salt mines it is, then ... I think that commit was quite the
wrong solution, I'll have to come up with something better. Sheeh, but
pools really are a total lossage in the presence of global caches.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 17 20:21:40 2006

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