public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastien dot decugis at ext dot bull dot net" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/300] New: pthread_cond_timedwait does not reacquire the mutex on cancelation
Date: Thu, 05 Aug 2004 08:19:00 -0000 [thread overview]
Message-ID: <20040805081906.300.sebastien.decugis@ext.bull.net> (raw)
On a 2-way box (2x i686) a cancelation handler sometimes fails to unlock the
mutex (errorcheck type) when the thread is canceled during
pthread_cond_timedwait operation.
The glibc is a CVS checkout from 2004-08-03, configured with NPTL support.
The compiler is gcc 3.4.1
The kernel is 2.6.7 #2 SMP Thu Jul 22 15:00:28 CEST 2004 i686 i686 i386 GNU/Linux
I can provide a sample to reproduce the problem (but it happens randomly :-( )
--
Summary: pthread_cond_timedwait does not reacquire the mutex on
cancelation
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: nptl
AssignedTo: drepper at redhat dot com
ReportedBy: sebastien dot decugis at ext dot bull dot net
CC: glibc-bugs at sources dot redhat dot com
http://sources.redhat.com/bugzilla/show_bug.cgi?id=300
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2004-08-05 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 8:19 sebastien dot decugis at ext dot bull dot net [this message]
2004-08-05 8:23 ` [Bug nptl/300] " sebastien dot decugis at ext dot bull dot net
2004-08-06 8:26 ` sebastien dot decugis at ext dot bull dot net
2004-08-06 15:13 ` jakub at redhat dot com
2004-08-09 21:42 ` jakub at redhat dot com
2004-08-11 18:51 ` rth at redhat dot com
2004-08-11 20:25 ` jakub at redhat dot com
2004-08-11 21:07 ` rth at gcc dot gnu dot org
2005-09-26 0:02 ` drepper at redhat dot com
2006-02-21 17:55 ` jakub at redhat dot com
2006-04-23 17:59 ` drepper at redhat dot com
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=20040805081906.300.sebastien.decugis@ext.bull.net \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@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).