Date: Thu, 29 Sep 2005 20:28:36 +0200 From: Simon Barner <barner@FreeBSD.org> To: Lefteris Tsintjelis <lefty@ene.asda.gr> Cc: freebsd-stable@freebsd.org, Simon Barner <barner@FreeBSD.org> Subject: Re: pthread_key_create memory leakage in pthreads? Message-ID: <20050929182836.GA4838@zi025.glhnet.mhn.de> In-Reply-To: <433BF441.80404@ene.asda.gr> References: <433BB81A.5090602@ene.asda.gr> <20050929133156.GA72022@zi025.glhnet.mhn.de> <433BF441.80404@ene.asda.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <other valgrind options> <command> You can put them into a file, say ~/.valgrind-suppressions, and tell valgrind to them with the --suppressions=3D<filename> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050929182836.GA4838>