On Jan 4, 2009, at 11:57 AM, Rainer Jung wrote:
Here's the gdb story:
When the content file gets opened, its cleanup is correctly
registered with the request pool. Later in core_filters.c at the end
of function ap_core_output_filter() line 528 we call
setaside_remaining_output().
This goes down the stack via ap_save_brigade(),
file_bucket_setaside() to apr_file_setaside(). This kills the
cleanup for the request pool and adds it instead to the transaction
(=connection) pool. There we are.
2.2.x has a different structure, although I can also see two calls
to ap_save_brigade() in ap_core_output_filter(), but they use
different pools as new targets, namely a deferred_write_pool resp.
input_pool.
Uggg... so we need to do the 'same' with the 2.3/2.4 arch
as well...
