Date: Thu, 29 Sep 2005 12:15:55 -0500 From: Dan Nelson <dnelson@allantgroup.com> 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: <20050929171554.GK68105@dan.emsphone.com> 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
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050929171554.GK68105>