From owner-freebsd-threads@FreeBSD.ORG Thu Sep 29 13:03:04 2005 Return-Path: X-Original-To: freebsd-threads@freebsd.org Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D16A16A428; Thu, 29 Sep 2005 13:03:04 +0000 (GMT) (envelope-from lefty@ene.asda.gr) Received: from mx3.asda.gr (ene.asda.gr [193.92.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50C2143D49; Thu, 29 Sep 2005 13:03:01 +0000 (GMT) (envelope-from lefty@ene.asda.gr) Received: by mx3.asda.gr (Postfix, from userid 58) id EF96D1146F; Thu, 29 Sep 2005 16:02:59 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ene.asda.gr X-Spam-Level: X-Spam-Status: score=-103.8 autolearn=ham tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST Received: from [193.92.118.162] (lefty.ene.asda.gr [193.92.118.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Lefteris Tsintjelis", Issuer "ASDA Root CA" (verified OK)) by mx3.asda.gr (Postfix) with ESMTP id 9CE871142D; Thu, 29 Sep 2005 16:02:53 +0300 (EEST) Message-ID: <433BE581.2080608@ene.asda.gr> Date: Thu, 29 Sep 2005 16:00:49 +0300 From: Lefteris Tsintjelis Organization: ASDA User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <433BBBD9.3070000@ene.asda.gr> <433BDFAA.6070307@freebsd.org> In-Reply-To: <433BDFAA.6070307@freebsd.org> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: pthread_key_create memory leakage in pthreads? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2005 13:03:04 -0000 David Xu wrote: > > The thread library is valgrind's version, the path is > /usr/local/lib/valgrind/libpthread.so.1, > it is not the native FreeBSD thread library. > > David Xu Yes, thats what it looked in the first place but I had a few doubts about how can he detect its own leakage. I know this is probably an off list topic but how can I reliably detect memory leakages, if any? Thnx, Lefteris