public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Jef Gearhart <jef@tpssys.com>
To: pthreads-win32@sources.redhat.com
Subject: [Fwd: Re: Unix vs. Windows Posix threads !]]
Date: Thu, 08 Jul 2004 14:58:00 -0000	[thread overview]
Message-ID: <40ED6116.6030207@tps.com> (raw)


I am re-forwarding this message to the pthread group, as the previous 
try bounced due to HTML formatting....

.................................
Lavanya,

Are using pthread_mutex_destroy() ?

Are you declaring local mutexes on the stack, or globally?

Mutexes are generally meant to be of global scope!

You need pthread_mutex_destroy(), or appropriate code reorganization.

I would not be surprised if you also have a handle leak on some of these 
other platforms.

Jef


Lavanya Swetharanyan wrote:

> I studied it further and I am getting "semaphore handle" leaks. The 
> number of semaphore handles keep growing. The handle viewer is not 
> giving me any other information.
> I am using the pthread_mutex_lock() and unlock, 
> pthread_mutex_init(&mutex,NULL); etc. and these are not giving me a 
> leak in MAC/Linux. What am I missing here ?.
>
>
>
>

             reply	other threads:[~2004-07-08 14:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 14:58 Jef Gearhart [this message]
2004-07-08 16:26 ` Lavanya Swetharanyan

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=40ED6116.6030207@tps.com \
    --to=jef@tpssys.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).