public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/1473] "pthread_cond_destroy()" hangs if called doubly on the same condvar on RHEL 4.0 Date: Sat, 15 Oct 2005 20:42:00 -0000 [thread overview] Message-ID: <20051015204241.6132.qmail@sourceware.org> (raw) In-Reply-To: <20051014053757.1473.arati_ph@yahoo.co.in> ------- Additional Comments From drepper at redhat dot com 2005-10-15 20:42 ------- It is not allowed to call pthread_cond_destroy twice. After the first call the memory is basically some uninitialized memory region. It is a program bug. Having said that, the current glibc version does try to help buggy programs a bit. You can check it out but if it does not work, don't ask for more changes. You have to fix your code instead. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID http://sourceware.org/bugzilla/show_bug.cgi?id=1473 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2005-10-15 20:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-14 5:38 [Bug nptl/1473] New: " arati_ph at yahoo dot co dot in 2005-10-14 5:39 ` [Bug nptl/1473] " arati_ph at yahoo dot co dot in 2005-10-14 5:49 ` arati_ph at yahoo dot co dot in 2005-10-15 20:42 ` drepper at redhat dot com [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=20051015204241.6132.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --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).