Thanks guys. Interesting info. It really helped.
On 01/12/2018 12:12 AM, Yann Ylavic wrote:
> On Thu, Jan 11, 2018 at 3:05 PM, Eric Covener wrote:
>> On Thu, Jan 11, 2018 at 3:55 AM, Simon Walter wrote:
>>>
>>> I suppose that the pool is keeping track of all it's allocations and if
>>> something
On Thu, Jan 11, 2018 at 3:05 PM, Eric Covener wrote:
> On Thu, Jan 11, 2018 at 3:55 AM, Simon Walter wrote:
>>
>> I suppose that the pool is keeping track of all it's allocations and if
>> something is still referenced, it will not free it.
>
> No the only tracking is done by whoever manages the
On Thu, Jan 11, 2018 at 3:55 AM, Simon Walter wrote:
> Hi everyone,
>
> Am I correct to assume that a pool cannot be forcibly (prematurely)
> freed? I was trying to understand apr_hash and wanted to free the memory
> allocated for the keys and then try a apr_hash_get. You know, put it
> through it
Hi everyone,
Am I correct to assume that a pool cannot be forcibly (prematurely)
freed? I was trying to understand apr_hash and wanted to free the memory
allocated for the keys and then try a apr_hash_get. You know, put it
through it's paces ;)
I read about apr_pool_clear:
"This does not actually
