Jeff Trawick <[EMAIL PROTECTED]> writes: > I think the problem is in the test programs (e.g., testprocmutex). As > soon as one child hits the specified number of iterations, the child > will exit and something like this will happen: > > #0 proc_mutex_sysv_cleanup (mutex_=0x804e608) at proc_mutex.c:205 > #1 0x4002dfa1 in run_cleanups (c=0x804e660) at apr_pools.c:1973 > #2 0x4002d59e in apr_pool_destroy (pool=0x804e4f8) at apr_pools.c:755 > #3 0x4002d58a in apr_pool_destroy (pool=0x804a4e8) at apr_pools.c:752 > #4 0x4002d24a in apr_pool_terminate () at apr_pools.c:585 > #5 0x4002a45d in apr_terminate () at start.c:117 > > And of course as soon as semctl(IPC_RMID) is done, the lock is broken.
No question in my mind. The problem is that Aaron cannot reproduce it... -- Philip Martin
