Re: [Valgrind-users] Problem with libpthread..

[Nicholas N. <nj...@ca...>]

On Fri, 6 Jun 2003, Joshua Moore-Oliva wrote:

> When I exit I notice that it appears there is a debug libpthread being used...
> So I'm thinking the problem is in valgrind debug pthread libraries itself.
>
> 200 bytes in 1 blocks are still reachable in loss record 1 of 1
> ==17060==    at 0x40215D2B: my_malloc (in /usr/lib/valgrind/libpthread.so)
> ==17060==    by 0x402178A2: get_or_allocate_specifics_ptr (in
> /usr/lib/valgrind/libpthread.so)
> ==17060==    by 0x402179D5: __pthread_key_create (in
> /usr/lib/valgrind/libpthread.so)
> ==17060==    by 0x805612C: main (main.c:57)
> ==17060==    by 0x4028CDC3: __libc_start_main (in /lib/libc-2.3.1.so)
> ==17060==    by 0x804BB90: (within
> /home/chatgris/code/mastermailings/code/daemons/list_manager/list_manager)

It's a leak in Valgrind's pthreads implementation, unfortunately.  We
added a suppression that will go into the next release -- actually fixing
the leak proved too difficult :(

So, you can ignore it.  If it's bugging you, you can use this suppression:

{
   my_malloc/get_or_allocate_specifics_ptr/__pthread_key_create(Leak)
   Memcheck:Leak
   fun:my_malloc
   fun:get_or_allocate_specifics_ptr
   fun:__pthread_key_create
}


N