Re: [Boost-users] valgrind reports memory still reachable when using shared_lock and shared_mutex

Subject: Re: [Boost-users] valgrind reports memory still reachable when using shared_lock and shared_mutex
From: Rajeev Rao (rbsrao79_at_[hidden])
Date: 2009-09-04 15:10:57

Thanks, that clears it up.  This is an off topic question, but what does AMDG mean. I assumed it meant that your comments are inline.

Rajeev

--- On Sat, 9/5/09, Steven Watanabe <watanabesj_at_[hidden]> wrote:

From: Steven Watanabe <watanabesj_at_[hidden]>
Subject: Re: [Boost-users] valgrind reports memory still reachable when using shared_lock and shared_mutex
To: boost-users_at_[hidden]
Date: Saturday, September 5, 2009, 12:35 AM

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

_______________________________________________
Boost-users mailing list
Boost-users_at_[hidden]
http://lists.boost.org/mailman/listinfo.cgi/boost-users