daedalus is running 2.0.32d

[Greg Ames <gr...@remulak.net>]

...as of Monday, 15-Apr-2002 19:15:03 PDT.  This has the patch for
ap_send_error_response to get rid of resource filters before trying to send a
canned HTTP error message,  That should make it functionally equivalent to how
it worked in 2.0.32.  I _think_ that will cure the majority of the seg faults.

But after I restarted httpd, I another core dump in /tmp from the old build. 
It's another mmap cleanup problem.  I haven't found a way to blame the mmap
problems on the canned error message bug in good conscience.  

Greg

/usr/local/apache2.0.35c/corefiles/httpd.core.4

#0  apr_pool_cleanup_kill (p=0x80d8868, data=0x815aa90,
    cleanup_fn=0x280cc700 <mmap_cleanup>) at apr_pools.c:1669
#1  0x280cc909 in apr_mmap_delete (mm=0x815aa90) at mmap.c:203
#2  0x280ad926 in mmap_destroy (data=0x81314a8) at apr_buckets_mmap.c:82
#3  0x280adf08 in apr_brigade_cleanup (data=0x8134590) at apr_brigade.c:86
#4  0x280adebe in brigade_cleanup (data=0x8134590) at apr_brigade.c:72
#5  0x280cdd3b in run_cleanups (c=0x8143610) at apr_pools.c:1713
#6  0x280cd51c in apr_pool_destroy (pool=0x8153010) at apr_pools.c:638
#7  0x805ea1c in ap_process_http_connection (c=0x812c120) at http_core.c:300
#8  0x806ecf3 in ap_run_process_connection (c=0x812c120) at connection.c:85
#9  0x806f008 in ap_process_connection (c=0x812c120, csd=0x812c048)
    at connection.c:207
#10 0x80648f0 in child_main (child_num_arg=135) at prefork.c:671

correction: daedalus is running 2.0.35d

[Greg Ames <gr...@remulak.net>]

Greg Ames wrote:
> 
> ...as of Monday, 15-Apr-2002 19:15:03 PDT. 

sorry about that.  The subject line in my previous email was wrong. 

Greg