apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Bloom <...@covalent.net>
Subject Re: Problem with memory initialization.
Date Thu, 06 Dec 2001 19:31:54 GMT
On Thursday 06 December 2001 11:23 am, Brian Pane wrote:
> Ryan Bloom wrote:
> >On Thursday 06 December 2001 11:11 am, Aaron Bannert wrote:
> >>>The biggest problem is that this would change the API for the one
> >>>function that must be in every APR program.
> >>>
> >>>Thoughts?
> >>
> >>Is it the lock routine or something specific to apr_pool_init that is
> >>creating the tmpfile? In general I think given the current state of
> >
> >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?!

That too is a good question.  I think that was a typo when we moved to the
new lock API, because the code is wrapped in #if APR_HAS_THREADS
logic.

Ryan

______________________________________________________________
Ryan Bloom				rbb@apache.org
Covalent Technologies			rbb@covalent.net
--------------------------------------------------------------

Mime
View raw message