On Thu, 1 Jun 2000, Gustavo Duarte wrote:
> there to see if it stops the problem (the code isn't too clean - lots of
> global variables, not written under strict, etc, but "it works").
looks like a global variable is exactly what your problem is. somebody is
creating an Apache::SubRequest object (via $r->lookup_{file,uri}, and it's
not going out of scope until the child exits. in this case, when
Apache::SubRequest::DESTROY is called, it calls destroy_sub_req() on a
pool that's already been cleared.
> #0 0x80a7407 in free_blocks ()
> #1 0x80a7660 in ap_clear_pool ()
> #2 0x80a76a1 in ap_destroy_pool ()
> #3 0x80be71a in ap_destroy_sub_req ()
> #4 0x8070d8a in XS_Apache__SubRequest_DESTROY ()
...
> #12 0x40077fa5 in perl_destruct () at perl.c:1008
> #13 0x80635a3 in perl_shutdown ()
> #14 0x80645c5 in perl_child_exit ()
