Subject: Re: [Boost-users] valgrind reports memory still reachable when using shared_lock and shared_mutex
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-09-04 15:05:23
AMDG
Rajeev Rao wrote:
>
> Could the problem be with the way I built the boost libraries? I used
> no options when doing the build.
>
>
> looks like boost::mutex doesn't have the problem (when used with
> unique_lock). So I guess the problem is in shared_mutex.
>
It isn't a problem. I thought I made that clear, but looking again,
it looks like I added a "not."
>> I understand that there are valid cases to expect reachable memory at
>> exit Should this be expected in this case ?
>>
>
> Yes. This is not expected, and there is no obvious way to change it.
Should read
> Yes. This is expected, and there is no obvious way to change it.
In Christ,
Steven Watanabe