Philip Martin wrote on 3/29/2006 6:24 PM:
> Malcolm Rowe <malcolm-svn-dev@farside.org.uk> writes:
>
>> On Wed, Mar 29, 2006 at 04:05:31PM +0100, Philip Martin wrote:
>>> Sviatoslav Sviridov <svd@altlinux.ru> writes:
>>>> ==22561== Jump to the invalid address stated on the next line
>>>> ==22561== at 0x44C0193: ???
>>>> ==22561== by 0x40A3BB6: pool_clear_debug (apr_pools.c:1361)
>>>> ==22561== by 0x40A3D1B: apr_pool_destroy_debug (apr_pools.c:1437)
>>>> ==22561== by 0x40A3BA6: pool_clear_debug (apr_pools.c:1358)
>>>> ==22561== by 0x40A3CAD: apr_pool_clear_debug (apr_pools.c:1411)
>>>> ==22561== by 0x4023C1E: main (svn_test_main.c:315)
>>>> ==22561== Address 0x44C0193 is not stack'd, malloc'd or (recently) free'd
>>> Are you building against the apr/apr-util that come in the Subversion
>>> tarball or are you using already installed apr/apr-util? If you are
>>> using already installed apr/apr-util you might try rebuilding
>>> apr/apr-util with --enable-pool-debug=yes.
>> Isn't that what the apr_pool_clear_debug in the backtrace indicates?
>
> It shows that Subversion is calling the debug functions, but what
> about already compiled code in the apr library? When apr_file_open,
> say, calls apr_pcalloc how will that call a debug function unless
> apr_file_open itself is recompiled?
I recompiled apr with --enable-pool-debug=yes, and then recompiled
subversion with that apr.
--
Best Regards,
Sviatoslav Sviridov
Received on Wed Mar 29 17:33:39 2006