From: Lavanya Swetharanyan <lavanya@psatellite.com>
To: Kok YihTzye-CYK011 <yihtzye.kok@motorola.com>
Cc: pthreads-win32@sources.redhat.com, "'Jef Gearhart'" <jef@tpssys.com>
Subject: Re: Unix vs. Windows Posix threads !
Date: Wed, 07 Jul 2004 20:56:00 -0000 [thread overview]
Message-ID: <2EC96D42-D058-11D8-BE46-000393C91F86@psatellite.com> (raw)
In-Reply-To: <47C7742111D3D511A01000D0B7B0C7C216171754@ZMY01EXM02>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
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 ?.
[-- Attachment #2: Type: text/enriched, Size: 398 bytes --]
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, <fixed>
pthread_mutex_init(&mutex,<color><param>3333,D1D1,3333</param>NULL</color>);
etc. and these are not giving me a leak in MAC/Linux. What am I
missing here ?.
</fixed>
next prev parent reply other threads:[~2004-07-07 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 20:34 Kok YihTzye-CYK011
2004-07-07 20:56 ` Lavanya Swetharanyan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 23:35 5qduh001
2004-07-07 17:46 Lavanya Swetharanyan
2004-07-07 17:54 ` Jef Gearhart
2004-07-07 18:09 ` Lavanya Swetharanyan
2004-07-07 19:31 ` Jef Gearhart
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=2EC96D42-D058-11D8-BE46-000393C91F86@psatellite.com \
--to=lavanya@psatellite.com \
--cc=jef@tpssys.com \
--cc=pthreads-win32@sources.redhat.com \
--cc=yihtzye.kok@motorola.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).