From owner-freebsd-stable@FreeBSD.ORG Thu Sep 29 17:16:09 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1022E16A41F; Thu, 29 Sep 2005 17:16:09 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 499B343D53; Thu, 29 Sep 2005 17:16:08 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j8THFtFn090192; Thu, 29 Sep 2005 12:15:55 -0500 (CDT) (envelope-from dan) Date: Thu, 29 Sep 2005 12:15:55 -0500 From: Dan Nelson To: Lefteris Tsintjelis Message-ID: <20050929171554.GK68105@dan.emsphone.com> References: <433BB81A.5090602@ene.asda.gr> <20050929133156.GA72022@zi025.glhnet.mhn.de> <433BF441.80404@ene.asda.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <433BF441.80404@ene.asda.gr> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org, Simon Barner Subject: Re: pthread_key_create memory leakage in pthreads? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Sep 2005 17:16:09 -0000 In the last episode (Sep 29), Lefteris Tsintjelis said: > Simon Barner wrote: > > > >Can you provide a (minimal) example where this happens? Also, what is > >the exact command line? > > valgrind --trace-children=yes --leak-check=yes --show-reachable=yes ./sql-m > > ==12024== 200 bytes in 1 blocks are definitely lost in loss record 3 of 5 > ==12024== at 0x3C03619F: malloc (in /usr/local/lib/valgrind/vgpreload_memcheck.so) > ==12024== by 0x3C0978EC: (within /usr/local/lib/valgrind/libpthread.so.1) > ==12024== by 0x3C09A2FD: (within /usr/local/lib/valgrind/libpthread.so.1) > ==12024== by 0x3C09A489: pthread_key_create (in /usr/local/lib/valgrind/libpthread.so.1) It's probably leakage internal to valgrind, since the stack trace stops inside a valgrind library. I wouldn't worry about it. -- Dan Nelson dnelson@allantgroup.com