public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: "pthreads-win32@sourceware.org" <pthreads-win32@sourceware.org>
Subject: Re: New release?
Date: Tue, 08 May 2012 01:21:00 -0000	[thread overview]
Message-ID: <4FA8751E.3010109@homemail.com.au> (raw)
In-Reply-To: <4FA81C37.1020008@cfengine.com>

Hi Eystein,

Yes, the 64 bit code in 2.8.0 was probably very dodgy. I believe CVS is 
stable at the moment so I will consider tagging it as 2.9.0.

ASAP.

Ross

On 8/05/2012 5:02 AM, Eystein Måløy Stenberg wrote:
> Hi,
>
> I have encountered a severe bug on a 64-bit MinGW build
> (http://mingw-w64.sourceforge.net/) of version 2.8.0.
>
> pthread_mutex_trylock always returns 0, no matter if the lock is held
> or not, and it never takes the lock. This causes pthread_mutex_destroy
> to always fail, and probably has other bad effects.
>
> To reproduce, try the following.
>
> ---
> int res_init = pthread_mutex_init(&mutex, NULL);
> int res_lock = pthread_mutex_lock(&mutex);
> int res_trylock = pthread_mutex_trylock(&mutex);
> int res_trylock2 = pthread_mutex_trylock(&mutex);
> int res_unlock = pthread_mutex_unlock(&mutex);
> int res_destroy = pthread_mutex_destroy(&mutex);
> printf("res_init=%d, res_lock=%d, res_trylock=%d, res_trylock2=%d,
> res_unlock=%d, res_destroy=%d\n", res_init, res_lock, res_trylock,
> res_trylock2, res_unlock, res_destroy);
> ---
>
> This seems to have been fixed in the latest cvs release. Since it has
> also been almost 6 years since the last release, could we please get a
> new release soon?
>
> Thank you.
>

      reply	other threads:[~2012-05-08  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 19:02 Eystein Måløy Stenberg
2012-05-08  1:21 ` 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=4FA8751E.3010109@homemail.com.au \
    --to=ross.johnson@homemail.com.au \
    --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).