From owner-freebsd-stable@FreeBSD.ORG Thu Sep 29 18:25:36 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 C91ED16A41F for ; Thu, 29 Sep 2005 18:25:36 +0000 (GMT) (envelope-from barner@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 785A243D4C for ; Thu, 29 Sep 2005 18:25:35 +0000 (GMT) (envelope-from barner@gmx.de) Received: (qmail invoked by alias); 29 Sep 2005 18:25:34 -0000 Received: from unknown (EHLO zi025.glhnet.mhn.de) [129.187.19.157] by mail.gmx.net (mp009) with SMTP; 29 Sep 2005 20:25:34 +0200 X-Authenticated: #147403 Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id A480AC112; Thu, 29 Sep 2005 20:28:36 +0200 (CEST) Date: Thu, 29 Sep 2005 20:28:36 +0200 From: Simon Barner To: Lefteris Tsintjelis Message-ID: <20050929182836.GA4838@zi025.glhnet.mhn.de> References: <433BB81A.5090602@ene.asda.gr> <20050929133156.GA72022@zi025.glhnet.mhn.de> <433BF441.80404@ene.asda.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline In-Reply-To: <433BF441.80404@ene.asda.gr> User-Agent: Mutt/1.5.10i X-Y-GMX-Trusted: 0 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 18:25:36 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Lefteris Tsintjelis wrote: > >Can you provide a (minimal) example where this happens? Also, what is > >the exact command line? >=20 > valgrind --trace-children=3Dyes --leak-check=3Dyes --show-reachable=3Dyes= ./sql-m Two other things you can try to determine whether it's you code or a internal error in valgrind: - make sure you compile and link your code with debugging information (-g), and at an reasonable optimization level (say -O). - Use valgrinds -v option to get more information. If you are sure, that's it's valgrind's fault, you can generate a suppression rule: valgrind -v --gen-suppressions=3Dyes You can put them into a file, say ~/.valgrind-suppressions, and tell valgrind to them with the --suppressions=3D switch. If you want to use them by default, create a ~/.valgrindrc file and put the appropriate options there. If all that doesn't help you, you're welcome to send me a copy of your code (in a private mail), and I'll have a look. --=20 Best regards / Viele Gr=FC=DFe, barner@FreeBSD.= org Simon Barner barner@gmx.de --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDPDJUCkn+/eutqCoRAqOgAJ9reJX+MnCUXpE/2gXqDOQdznOlvQCgz/nx 9e4rW+oLNabxeeFjJdWOEUA= =SUS9 -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2--