apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Bannert <aa...@clove.org>
Subject Re: testglobalmutex.c
Date Mon, 15 Mar 2004 19:17:33 GMT

On Mar 15, 2004, at 11:15 AM, Aaron Bannert wrote:
> On Mar 15, 2004, at 10:56 AM, rbb@rkbloom.net wrote:
>> Nope.  Take a look at the thread that is complaining about the API for
>> global_mutex and proc_mutex.  Without that global_mutex_create call, 
>> the program
>> segfaults on any Unix machine.  This is a bug in the _child_init API, 
>> because it
>> should accept a lockmech_e argument so that the lock can be created 
>> properly.
>
> Actually the bug is that the unix implementation of 
> apr_global_mutex_child_init
> assumes the (apr_global_mutex **mutex) is valid, and it shouldn't.

Oh hey, look at me, repeating the previous sentence. Maybe I need more 
sleep. :)

-aaron


Mime
View raw message