Re: [Boost-users] Boost.Thread memory leak reported

25 Aug 2005


      ...
-----Original Message-----
From: boost-users-bounces@lists.boost.org 
[mailto:boost-users-bounces@lists.boost.org] On Behalf Of 
Christian Henning
Sent: Thursday, August 25, 2005 10:53 AM
To: boost-users@lists.boost.org
Subject: Re: [Boost-users] Boost.Thread memory leak reported
On 8/25/05, Sohail Somani  wrote:
...
Valgrind doesn't find it either. I have yet to try it with stack 
walker (was about to but xp blue screened so I took it as a sign)
Isn't valgrind for linux? I think the problem might be on 
Windows machines, only.
The functions new_critical_section() and 
delete_critical_section() should be called only on Windows 
machines, since they are calling Win32 functions.
I didn't know it was a Windows only problem until you posted the
location of the leaked allocation.