Stas Bekman <[EMAIL PROTECTED]> writes: [...]
> > Any ideas about how to fix the segfaults at startup time too? > > I'll try to reproduce it now. I'm able to get these segfults now, but not reliably. My first impression is that some APR::Pool SV object created during post-config, and points at the ptemp pool. The problem seems to be that the SV has a slightly longer lifespan than the pool does, so when DESTROY is called on the SV, the (ptemp) pool pointer it has is bogus. I think APR__Pool.h would be better insulated from this sort of bug if it stored the SV's "can call apr_pool_destroy" status in the SV's magic table, instead of the pool's userdata. -- Joe Schaefer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
