public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <rpj@ise.canberra.edu.au>
To: phuong nguyen <phuong@xambala.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: pthread_mutex_lock leaking memory?
Date: Sat, 30 Aug 2003 02:35:00 -0000	[thread overview]
Message-ID: <3F500D2A.7010700@ise.canberra.edu.au> (raw)
In-Reply-To: <45EC781FB567314B862CEA4CC72ABF0C05974C@sj-ex-02.xambala.local>

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 
pthread_mutex_init().

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, 
Rational TestSuite

See
http://www.rational.com/docs/v2003/unix_solutions/html/legal_information.html?SMSESSION=NO

Ross

phuong nguyen wrote:

>Hi
>
>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
>pthread_setcanceltype.
>
>Phuong
>  
>

      reply	other threads:[~2003-08-30  2:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 21:00 phuong nguyen
2003-08-30  2:35 ` Ross Johnson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F500D2A.7010700@ise.canberra.edu.au \
    --to=rpj@ise.canberra.edu.au \
    --cc=phuong@xambala.com \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).