public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug linuxthreads/739] pthread_getspecific / pthread_setspecific broken if single-threaded Date: Wed, 16 Feb 2005 11:26:00 -0000 [thread overview] Message-ID: <20050216112652.4679.qmail@sourceware.org> (raw) In-Reply-To: <20050216044910.739.roland@gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-16 11:26 ------- Subject: Bug 739 CVSROOT: /cvs/glibc Module name: libc Branch: glibc-2_3-branch Changes by: roland@sources.redhat.com 2005-02-16 11:26:40 Modified files: linuxthreads : Makefile specific.c Log message: 2005-02-07 Jakub Jelinek <jakub@redhat.com> [BZ #739] * specific.c (pthread_key_delete): If pthread_create has not been called yet, clear p_specific for the current thread. * Makefile (tests): Add tst-tsd1. * tst-tsd1.c: New test. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/linuxthreads/Makefile.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.96.2.1&r2=1.96.2.2 http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/linuxthreads/specific.c.diff?cvsroot=glibc&only_with_tag=glibc-2_3-branch&r1=1.20&r2=1.20.4.1 -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=739 ------- 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:[~2005-02-16 11:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-16 4:49 [Bug linuxthreads/739] New: " roland at gnu dot org 2005-02-16 11:26 ` cvs-commit at gcc dot gnu dot org [this message] 2005-02-16 11:27 ` [Bug linuxthreads/739] " cvs-commit at gcc dot gnu dot org 2005-04-05 23:59 ` roland at gnu dot org
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=20050216112652.4679.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).