From: "Mark Pizzolato - pthreads - win32" <MarkPizzolato-pthreads-win32@subscriptions.pizzolato.net>
To: <pthreads-win32@sourceware.org>
Subject: Win32 pthread bugs
Date: Fri, 31 Dec 2010 18:47:00 -0000 [thread overview]
Message-ID: <78FD0775812F9E429FF9F5E1AA158DBE409623@redroof.alohasunset.com> (raw)
The code in sched_setscheduler() and sched_getscheduler() each leaks a
handle which is opened, never used and then left open.
These should probably be fixed.
- Mark Pizzolato
next reply other threads:[~2010-12-31 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 18:47 Mark Pizzolato - pthreads - win32 [this message]
2011-02-27 0:39 ` Ross Johnson
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=78FD0775812F9E429FF9F5E1AA158DBE409623@redroof.alohasunset.com \
--to=markpizzolato-pthreads-win32@subscriptions.pizzolato.net \
--cc=pthreads-win32@sourceware.org \
/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).