At 01:43 AM 7/20/2005, Joe Orton wrote: >Is this refactoring complete? Apart from the compiler warnings, a bunch >of the t/ssl/proxy.t tests have started failing with the trunk code. >With worker, the server is dumping core: > >(this seems to be a regression since 2005-07-15, when all the tests were >passing with both prefork and worker)
Hmmm. The perl-framework doesn't generate any cores against 2.0.x with my proposed patches (backport of this refactoring)... I'm guessing it's a subtle bug in the bucket or brigade allocation if this is specific to the patch. But because only this single case actually segfaults for you, I'm concerned we might have found an edge case elsewhere in the code. >#2 apr_pool_clear (pool=0x0) at memory/unix/apr_pools.c:332 > freelist = (apr_memnode_t *) 0x0 > max_index = 2 > max_free_index = 0 > next = (apr_memnode_t *) 0x56a3e8 > index = 0 > current_free_index = 4294967295 Evidently an allocation issue... since we don't touch the issue until we hit the cleanups. >#4 0x0000002a97de95a6 in ap_proxy_release_connection (proxy_function=0x56a3e8 >"\001", conn=0x809cd8, s=0x0) at >proxy_util.c:1714 >No locals. >#5 0x0000002a980fd6c8 in ap_proxy_http_cleanup (scheme=0x0, r=0x89e4d8, > backend=0x809cd8) at mod_proxy_http.c:1525 >No locals. >#6 0x0000002a980fe910 in proxy_http_handler (r=0x89e4d8, >worker=0x5a0328, > conf=0x878b88, url=0x891168 "/require-ssl-cgi/env.pl", proxyname=0x0, > proxyport=0) at mod_proxy_http.c:1162 > here = (struct apr_bucket *) 0x0 > status = 0 > server_portstr = > ":8541\000\000\000Húj\225*\000\000\000ÿÿÿÿ\000\000\000\000\210\213\207\000\000\000\000" > scheme = 0x0 > proxy_function = 0x2a980fee00 "HTTPS" > u = 0x0 > backend = (proxy_conn_rec *) 0x809cd8 > is_ssl = 1 > p = (apr_pool_t *) 0x8903f8 > uri = (apr_uri_t *) 0x8910a8 I'm going to spend some time this afternoon in the perl-framework, see what I can come up with. Bill
