From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3407 invoked by alias); 12 Oct 2006 05:59:07 -0000 Received: (qmail 3043 invoked by uid 48); 12 Oct 2006 05:58:56 -0000 Date: Thu, 12 Oct 2006 05:59:00 -0000 Message-ID: <20061012055856.3042.qmail@sourceware.org> From: "ian at airs dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20061007013816.3317.ian@airs.com> References: <20061007013816.3317.ian@airs.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug nptl/3317] Overriding free which clobbers data and calls pthread_getspecific can get bad value X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2006-10/txt/msg00061.txt.bz2 List-Id: ------- 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.