Branko ÄŒibej <brane@xbc.nu> writes:
> So, I'd like to ask people to check out HEAD, compile and run this
> test on as many machines as possible, and post the output. 100000
> repetitions would take about 5 hours on my box (450MHz PIII).
It runs successfully on my x86 Linux box under valgrind, compiled with
APR_POOL_DEBUG=1 and without optimisation (100000 iterations would
take over a month :-)
$ valgrind subversion/tests/libsvn_delta/.libs/lt-random-test -n10 2
==30848== valgrind-1.0pre1, a memory error detector for x86 GNU/Linux.
==30848== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
==30848== Estimated CPU clock rate is 451 MHz
==30848== For more details, rerun with: -v
==30848==
SEED: random combine delta test, seed = 350685093
SEED: Last seen = 1846555367
PASS: lt-random-test 2: random combine delta test, seed = 350685093
==30848== pthread_mutex_unlock: mutex is not locked
==30848== at 0x403AB4BF: (within /usr/lib/valgrind/libpthread.so)
==30848== by 0x40339043: thread_mutex_cleanup (thread_mutex.c:67)
==30848== by 0x4033BCD2: run_cleanups (apr_pools.c:1940)
==30848== by 0x4033B3B9: pool_clear_debug (apr_pools.c:1361)
==30848==
==30848== ERROR SUMMARY: 5 errors from 1 contexts (suppressed: 60 from 1)
==30848== malloc/free: in use at exit: 0 bytes in 0 blocks.
==30848== malloc/free: 2846 allocs, 2846 frees, 18103340 bytes allocated.
==30848== For a detailed leak analysis, rerun with: --leak-check=yes
==30848== For counts of detected errors, rerun with: -v
The pthread errors are coming from APR, thread_mutex_cleanup calls
pthread_mutex_unlock when destroying a mutex. I suppose the author
wanted to ensure it was unlocked, but it's strictly undefined
behaviour.
--
Philip
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 20 02:07:11 2002