apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tacalau Daniel Stefan <daniel.taca...@avira.com>
Subject Re: Problem with pool integrity check for apr threads
Date Thu, 13 Sep 2007 08:22:11 GMT
Joe Orton wrote:
> I guess this is one part of the pool-debug code which never got tested!  
> This can be fixed either by some convoluted hack to change the pool 
> ownership after apr_thread_create(), or simply by moving the thread 
> creation later in apr_thread_create().  The latter would be simpler.  
> Can you file a bug on this in bugzilla?
>
> joe
>   
Thread creation is the last operation done by apr_thread_create(). A
solution would be for apr_thread_exit() to not call apr_pool_destroy()
since it the exiting thread does now own the pool and leave this to the
thread parent. This will comply with apr_pool_check_integrity requirements.

How important is the apr_pool_check_integrity's owneship test (do not
release on a thread resources allocated in  a pool that belongs to
another thread)? Can this lead to crashes or leaks?

I'll fill a bug report!

-- 
Best regards,

Daniel Tacalau


Mime
View raw message