I've seen this same thing in the last couple days, but I'm not able to reliably reproduce it. What did you have to do to get to this state (a null filter it looks like)?
-aaron On Fri, Apr 05, 2002 at 05:03:56PM -0500, Dale Ghent wrote: > Aye! I've ran into one core dump, but it seems to be PHP-4.3.0-dev > related, passing a NULL to ap_save_brigade(). > > #0 0x72dfc in ap_save_brigade (f=0x0, saveto=0x20bc5c, b=0xffbef640, > p=0x276110) at util_filter.c:562 > 562 APR_BRIGADE_CONCAT(*saveto, *b); > > (gdb) where > #0 0x72dfc in ap_save_brigade (f=0x0, saveto=0x20bc5c, b=0xffbef640, > p=0x276110) at util_filter.c:562 > > #1 0xfee7e268 in php_output_filter (f=0x27f658, bb=0x27f760) > at /local/src/apache-dev/php4/sapi/apache2filter/sapi_apache2.c:354 > > #2 0x72d30 in ap_pass_brigade (next=0x27f658, bb=0x2043d8) > at util_filter.c:534 > > #3 0x7a02c in default_handler (r=0x27ed38) at core.c:3247 > > #4 0x6643c in ap_run_handler (r=0x27ed38) at config.c:193 > > #5 0x66900 in ap_invoke_handler (r=0x27ed38) at config.c:373 > > #6 0x3ac18 in ap_internal_redirect (new_uri=0x27ed38 "", r=0x27ed38) > at http_request.c:458 > > #7 0x3a76c in ap_process_request (r=0x276148) at http_request.c:274 > > #8 0x36158 in ap_process_http_connection (c=0x2003a8) at http_core.c:291 > > #9 0x70bdc in ap_run_process_connection (c=0x2003a8) at connection.c:85 > > #10 0x64cb4 in child_main (child_num_arg=20014) at prefork.c:671 > > #11 0x64e9c in make_child (s=0x64400, slot=5) at prefork.c:765 > > #12 0x650d4 in perform_idle_server_maintenance (p=0xbc408) at > prefork.c:900 > > #13 0x65704 in ap_mpm_run (_pconf=0x1, plog=0xb2000, s=0x0) at > prefork.c:1092 > > #14 0x6a9fc in main (argc=1784280, argv=0xba480) at main.c:622 >
