This is the mail archive of the
mailing list for the pthreas-win32 project.
Re: pthread_mutex_lock leaking memory?
- From: Ross Johnson <rpj at ise dot canberra dot edu dot au>
- To: phuong nguyen <phuong at xambala dot com>
- Cc: pthreads-win32 at sources dot redhat dot com
- Date: Sat, 30 Aug 2003 12:34:18 +1000
- Subject: Re: pthread_mutex_lock leaking memory?
- References: <45EC781FB567314B862CEA4CC72ABF0C05974C@sj-ex-02.xambala.local>
- Reply-to: rpj at ise dot canberra dot edu dot au
I don't see how pthread_setcanceltype() is called through a mutex lock
on a PTHREAD_MUTEX_INITIALIZER mutex. Also, once the mutex is first
locked, the mutex is then like any other mutex initialised through
Can you send a short code fragment that demonstrates the leak? Also,
some information on how you're running the library if it's unusual
(static linked etc).
BTW, I see that Rational (now IBM) lists pthreads-win32 amongst it's
third party components for the following products:
Rational Test Manager, Rational Quality Architect, Rational Robot,
phuong nguyen wrote:
I'm using 5-10-03 snapshot of pthread-win32 with MSVC 6.0 SP5. It seems
that when I init a mutex with PTHREAD_MUTEX_INITIALIZER, it would leaks
44 bytes of memory when ever I do a lock on the mutex. Any one else
encounter the same problem? Rational Purify trace the leak back to