public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugzilla at merlin dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug linuxthreads/373] New: pthread_key_delete does not NULL key values prior to pthread_create Date: Wed, 08 Sep 2004 21:09:00 -0000 [thread overview] Message-ID: <20040908210923.373.bugzilla@merlin.org> (raw) Normally pthread_key_create should return a new key with NULL values. LinuxThreads relies on pthread_key_delete to NULL the key value in order to achieve this. However it does not do this in an application prior to pthread_create being called, so if an app does: pthread_key_create() ... pthread_setspecific(non-null) ... pthread_key_delete() ... pthread_key_create() then the new key will have the old non-null value. I'm not familiar enough with POSIX to know if this behaviour is acceptable, but it is annoying in an app where threads are sometimes not created for some time. Linux 2.4.25/i386/glibc 2.3.2/LinuxThreads-0.10 -- Summary: pthread_key_delete does not NULL key values prior to pthread_create Product: glibc Version: 2.3.2 Status: NEW Severity: normal Priority: P2 Component: linuxthreads AssignedTo: gotom at debian dot or dot jp ReportedBy: bugzilla at merlin dot org CC: glibc-bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=373 ------- 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-09-08 21:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-08 21:09 bugzilla at merlin dot org [this message] 2004-09-08 21:12 ` [Bug linuxthreads/373] " bugzilla at merlin dot org 2004-09-09 16:36 ` gotom at debian dot or dot jp
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=20040908210923.373.bugzilla@merlin.org \ --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: linkBe 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).