On Fri, 18 Jul 2003, Brad Nicholes wrote:

> more threads could overwrite parent->child simply because the wrong
> mutex was locked or no mutex was locked at all (in our case).  The call
> to apr_allocator_mutex_get() should use "parent->allocator" not
> "allocator".  If you look at apr_pool_destroy() it is doing it
> correctly.  Otherwise this code is not thread safe.

Ouch!!  Good catch.  :)

Reply via email to