Philippe M. Chiasson wrote:
Joe Orton wrote:
Right; the thing is that currently, there really is no way to actually "free the brigade"; apr_brigade_destroy() just does an apr_brigade_cleanup() and unregisters the pool cleanup. The brigade structure remains valid until the pool it's allocated from gets destroyed.
To help track down the bug:
1) build httpd/apr* with -DAPR_BUCKET_DEBUG to enable the brigade consistency checks; this may show very quickly the problem
Philippe, can you please do that? I don't get this problem so it's probably the best that you do that.
Just updated to httpd 2.0.50-dev latest and recompiled with all the APR_DEBUG_*
I could fine, still same exact core dump ;(
I've never used that flag. I suppose it doesn't prevent segfaults but probably generates a copious diagnostics output.
Nah, in the case of APR_BUCKET_DEBUG, it only makes one little extra check when
deleting buckets in apr_bucket_free :
valgrind?
Though I think even if we find who did it, it doesn't help us much, since any filter can do that in the future, causing the same effect. I suppose we ought to rewrite it to use a less efficient implementation which will create and destroy $bb every time it enters the loop. :(
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
