public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: Mark Pizzolato - pthreads - win32
	<MarkPizzolato-pthreads-win32@subscriptions.pizzolato.net>
Cc: pthreads-win32@sourceware.org
Subject: Re: Win32 pthread bugs
Date: Sun, 27 Feb 2011 00:39:00 -0000	[thread overview]
Message-ID: <4D699D4C.7070508@homemail.com.au> (raw)
In-Reply-To: <78FD0775812F9E429FF9F5E1AA158DBE409623@redroof.alohasunset.com>

On 1/01/2011 5:47 AM, Mark Pizzolato - pthreads - win32 wrote:
> 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
>
This is now fixed in CVS. It affects calls where the argument PID is not 
the current PID, in which case the code tries to determine if PID is 
valid only.

Thanks.

      reply	other threads:[~2011-02-27  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-31 18:47 Mark Pizzolato - pthreads - win32
2011-02-27  0:39 ` 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=4D699D4C.7070508@homemail.com.au \
    --to=ross.johnson@homemail.com.au \
    --cc=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).