apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cliff Woolley <jwool...@virginia.edu>
Subject Re: Creating an allocator with no mutex...
Date Fri, 18 Jul 2003 21:38:26 GMT
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.  :)

View raw message