From: wtc@netscape.com (Wan-Teh Chang)
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Two IA-64 Linux bugs
Date: Wed, 07 Jun 2000 14:57:21 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205126@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205116@msgid-missing>
"Boehm, Hans" wrote:
>
> We also had problems around here with pthread_cond_wait. The glibc version
> we were using was used a linuxthreads snapshot taken at a bad time.
> Pthread_cond_wait checked that the current thread owned the mutex.
> Unfortunately, it did so even for "fast" mutexes, for which the owner field
> wasn't set.
>
> If this is the problem, I would guess that you should be able to avoid it by
> using recursive or checking mutexes. The problem is hopefully very
> temporary, since the glibc on sourceware exhibited this problem for only a
> day.
Indeed, if I use a recursive or error-checking mutex,
I cannot make my test case (pingpong.c) fail.
Wan-Teh
prev parent reply other threads:[~2000-06-07 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 5:44 [Linux-ia64] Two IA-64 Linux bugs Wan-Teh Chang
2000-06-05 20:42 ` Dan Pop
2000-06-05 20:58 ` Bill Nottingham
2000-06-05 22:10 ` Dan Pop
2000-06-06 17:08 ` Boehm, Hans
2000-06-07 14:57 ` Wan-Teh Chang [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=marc-linux-ia64-105590678205126@msgid-missing \
--to=wtc@netscape.com \
--cc=linux-ia64@vger.kernel.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