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 14:44:33

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. 

Rajeev

--- On Thu, 9/3/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: Thursday, September 3, 2009, 9:40 AM

AMDG

Rajeev Rao wrote:
> I found similar problems when getting an exclusive lock via unique_lock as well. I wrote this test code to reproduce. I get the still-reachable problem if I use either the read() or the write() call (shared_lock or
 unique_lock). Multiple calls to these functions  did not increase the number of reachable bytes in the valgrind report. I understand my previous use of adopt_lock was undefined (hence i've not used it here). Is my use as described by the code correct now ? If so, is this a bug ?
>   

It is almost certainly exactly the same as with shared_lock.  The
code that allocates the object is in a lower level component.

In Christ,
Steven Watanabe

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