Stefan Hett <ste...@egosoft.com> writes: > Looks like the dumps are from a VisualSVN Server compiled version. Did you > try contacting their support? Without the PDBs from their compiled version > it's a bit difficult for other users like me to check the crash out...
Here is a proper stacktrace of the crash, reassembled with debug symbols: libapr-1.dll!allocator_free(apr_allocator_t *allocator, apr_memnode_t *node) at apr/memory/unix/apr_pools.c:381 libsvn_ra-1.dll!serf_headers_destroy_and_data(serf_bucket_t *bucket) at serf/buckets/headers_buckets.c:245 libsvn_ra-1.dll!serf_response_destroy_and_data(serf_bucket_t *bucket) at serf/buckets/response_buckets.c:117 libsvn_ra-1.dll!clean_resp(void * data) at serf/outgoing.c:54 libapr-1.dll!apr_pool_destroy(apr_pool_t *pool) at apr/memory/unix/apr_pools.c:814 libapr-1.dll!apr_pool_destroy(apr_pool_t *pool) at apr/memory/unix/apr_pools.c:811 libapr-1.dll!apr_pool_destroy(apr_pool_t *pool) at apr/memory/unix/apr_pools.c:811 libapr-1.dll!apr_pool_destroy(apr_pool_t *pool) at apr/memory/unix/apr_pools.c:811 libsvn_subr-1.dll!svn_cmdline_handle_exit_error(...) at subversion/subversion/libsvn_subr/cmdline.c:422 ... Looks like a pool lifetime issue to me; perhaps similar to the one that was discussed and fixed in [1]. [1] https://groups.google.com/d/msg/serf-dev/gOn9HTUN98U/pz0_AqdrmJYJ Regards, Evgeny Kotkov