From: Dmitrii Sernii <bogolt@gmail.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: Handle leak when using pthread mutex with win32 api threads
Date: Sun, 06 Mar 2005 08:54:00 -0000 [thread overview]
Message-ID: <1335432268.20050306104111@gmail.com> (raw)
>> I've made small corrections in test sample, so now mutex initialised
>> only once, and i've added pthread_mutex_destroy() function call. But
>> the problem still remains.
>> Here is two test applications - one of them uses API threads, and the
>> other pthreads. Program with pthreads don't have any leaks, while
>> program with API threads produces lots of them.
>>
RJ> Are you dynamic or static linking? If you're using the pthreads dll then
RJ> there would seem to be a problem in the library. If you're static
RJ> linking then read on ...
I'm using pthreads dll.
Best regards,
Dmitrii Sernii
next reply other threads:[~2005-03-06 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 8:54 Dmitrii Sernii [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 12:51 Bossom, John
2005-03-05 13:31 Dmitrii Sernii
2005-03-05 21:41 ` Ross Johnson
2005-03-08 1:22 ` Ross Johnson
2005-03-04 15:53 Dmitry Sernii
2005-03-04 17:06 ` Gottlob Frege
2005-03-04 22:27 ` Ross Johnson
2005-03-04 17:07 ` Gottlob Frege
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=1335432268.20050306104111@gmail.com \
--to=bogolt@gmail.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).