public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/3317] Overriding free which clobbers data and calls pthread_getspecific can get bad value Date: Thu, 12 Oct 2006 05:59:00 -0000 [thread overview] Message-ID: <20061012055856.3042.qmail@sourceware.org> (raw) In-Reply-To: <20061007013816.3317.ian@airs.com> ------- Additional Comments From ian at airs dot com 2006-10-12 05:58 ------- That was, of course, just an example which tests for whether the problem exists. The issue is overriding malloc(), free() and friends, where they use pthread specific keys, and where free clobbers the block data for debugging purposes. Since the pthread code itself calls free, it is impossible for free to know whether or not the pthread specific key has been destroyed. The only way is for free to check whether pthread_get_specific returns NULL, but that doesn't work if it clobbers the data for debugging purposes. I can't say that I'm surprised that you plan to ignore this bug report. However, I hope the report will give a hint to distros to swap the order of those two lines. -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | http://sourceware.org/bugzilla/show_bug.cgi?id=3317 ------- 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:[~2006-10-12 5:59 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-07 1:38 [Bug nptl/3317] New: " ian at airs dot com 2006-10-07 1:39 ` [Bug nptl/3317] " ian at airs dot com 2006-10-07 20:46 ` drepper at redhat dot com 2006-10-12 5:59 ` ian at airs dot com [this message] 2006-10-12 21:18 ` drepper at redhat dot com 2006-10-13 5:26 ` ian at airs 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=20061012055856.3042.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).