httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: segfault ap_save_brigage in the latest 2.0
Date Mon, 27 Sep 2004 12:29:35 GMT
Cliff Woolley wrote:
[...]
> Looking at the ->prev pointer of b, it seems that the pointer there is way
> out of range compared to the other pointer values you gave.  And brigade b
> is obviously corrupt, so... yeah.  So the question is, at what point did
> brigade b get corrupted.  The easiest way to find that out is to enable
> brigade debugging -- that way, any time you do any manipulations to the
> brigade that could potentially corrupt it, it will sanity-check the ring
> pointers in both directions for you.  That way it will assert when the
> corruption happens rather that some arbitrary time in the future, which is
> what you're seeing here.

Thanks Cliff, and how do I enable that?

-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Mime
View raw message