apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sander Striker" <stri...@apache.org>
Subject RE: Problem with memory initialization.
Date Thu, 06 Dec 2001 19:49:55 GMT
> From: Ryan Bloom [mailto:rbb@covalent.net]
> Sent: 06 December 2001 20:34

> On Thursday 06 December 2001 11:29 am, Aaron Bannert wrote:
> > On Thu, Dec 06, 2001 at 11:23:44AM -0800, Brian Pane wrote:
> > > >It is the apr_pool_init function, which is creating the lock with a NULL
> > > >fname, so it is a bigger problem than just the pool lock.
> > >
> > > Why is the pool initialization creating a crossprocess lock?!
> >
> > The only place where I see this happening is in the shmem.c code.
> > Other than that I don't see anywhere else in APR/APR-UTIL that
> > is creating a CROSS_PROCESS or LOCKALL scoped lock.
> >
> > Perhaps it's just the accept mutex in httpd?
> 
> Damn, you're right, this is an INTRAPROCESS lock.  Gotta keep
> looking for the real culprit I guess.  Regardless, why is APR still using
> the old lock API?

Now I understand why I, in confused mode, had a cross process lock
in my new pools code.  I mistakenly copied the locking logic.

> Ryan

Sander

Mime
View raw message