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] pthread_key_delete does not NULL key values prior to pthread_create Date: Wed, 08 Sep 2004 21:12:00 -0000 [thread overview] Message-ID: <20040908211231.32211.qmail@sourceware.org> (raw) In-Reply-To: <20040908210923.373.bugzilla@merlin.org> ------- Additional Comments From bugzilla at merlin dot org 2004-09-08 21:12 ------- Created an attachment (id=188) --> (http://sources.redhat.com/bugzilla/attachment.cgi?id=188&action=view) demonstration of pthread_key_create/delete issue Compile: gcc -pthread a.c -lpthread Run: ./a.out As printed, the initial key value is non-NULL for a reused key that was deleted prior to invoking pthread_create(). -- 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 prev parent reply other threads:[~2004-09-08 21:12 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-08 21:09 [Bug linuxthreads/373] New: " bugzilla at merlin dot org 2004-09-08 21:12 ` bugzilla at merlin dot org [this message] 2004-09-09 16:36 ` [Bug linuxthreads/373] " 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=20040908211231.32211.qmail@sourceware.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).