On Fri, Jun 24, 2011 at 07:27:44PM +0200, Stefan Sperling wrote:
> I don't know if this is already known, so I am reporting it
> here to get confirmation.
>
> (From #svn-dev):
> <stsp> run svn log --diff -r1139384 for fun
> <stsp> with serf
> <stsp> Ctrl-C out in the middle when it prints diff text
> <stsp> -> core dump
> <stsp> #0 0x0000000204cef469 in destroy_request (request=0x2083f47b8)
> <stsp> at ./outgoing.c:309
> <stsp> 309 serf_debug__closed_conn(request->req_bkt->allocator);
> <stsp> (gdb) p *request->req_bkt
> <stsp> Cannot access memory at address 0x20d41f1b8
> <stsp> is this known?
I suppose a proper backtrace would be useful:
(gdb) bt
#0 0x0000000204cef469 in destroy_request (request=0x2083f47b8)
at ./outgoing.c:309
#1 0x0000000204cef590 in cancel_request (request=0x2083f47b8,
list=0x20d3dd0d0, notify_request=0) at ./outgoing.c:350
#2 0x0000000204cf0ce9 in serf_request_cancel (request=0x2083f47b8)
at ./outgoing.c:1268
#3 0x0000000204cf088d in serf_connection_close (conn=0x20d3dd028)
at ./outgoing.c:1113
#4 0x0000000204ceeee5 in clean_conn (data=0x20d3dd028) at ./outgoing.c:56
#5 0x000000020b08e1b2 in run_cleanups (cref=0x208923048)
at /home/stsp/svn/src/apr-1.4.5/memory/unix/apr_pools.c:2346
#6 0x000000020b08d158 in apr_pool_destroy (pool=0x208923028)
at /home/stsp/svn/src/apr-1.4.5/memory/unix/apr_pools.c:809
#7 0x000000020b08d13e in apr_pool_destroy (pool=0x20be29028)
at /home/stsp/svn/src/apr-1.4.5/memory/unix/apr_pools.c:806
#8 0x000000020b08d13e in apr_pool_destroy (pool=0x205451028)
at /home/stsp/svn/src/apr-1.4.5/memory/unix/apr_pools.c:806
#9 0x000000020b08d13e in apr_pool_destroy (pool=0x20a7f5028)
at /home/stsp/svn/src/apr-1.4.5/memory/unix/apr_pools.c:806
#10 0x000000020b08d13e in apr_pool_destroy (pool=0x208f2d028)
at /home/stsp/svn/src/apr-1.4.5/memory/unix/apr_pools.c:806
#11 0x00000000004156bd in main (argc=5, argv=0x7f7ffffc0f90)
at subversion/svn/main.c:2614
