On Thu, Sep 07, 2006 at 11:22:35AM -0400, Jeff Trawick wrote: > It would be cool for the MPM to be able to lock the pool once it is > ready to start serving requests so that if any errant module tries to > use pconf, pchild, etc. it will crash immediately instead of > introducing memory corruption under load. (Even if the module author > is "clever" and uses a mutex around the pool use, that assumes she is > the only person in the world to have that idea.)
If done "#if APR_POOL_DEBUG", I think this would be useful. Would need to be clear about whether other ways of manipulating the pool (userdata, cleanups, clear, destroy?) are covered or really just apr_p*alloc. > Some other multi-threaded APR apps probably have the same concern, > especially if they allow plug-ins from third parties to be loaded. > > apr_pool_lock() - cause abort() on subsequent allocation request [un-implemented, un-documented apr_pool_lock() already in-tree!] joe
