|
From: Nicholas N. <nj...@ca...> - 2004-04-15 08:03:19
|
> ==21781== 200 bytes in 1 blocks are definitely lost in loss record 2 of 2
> ==21781== at 0x3C01E250: malloc (vg_replace_malloc.c:105)
> ==21781== by 0x3C025DF6: my_malloc (vg_libpthread.c:334)
> ==21781== by 0x3C028AAA: get_or_allocate_specifics_ptr
> (vg_libpthread.c:1591)
> ==21781== by 0x3C028C33: pthread_key_create (vg_libpthread.c:1628)
This is an leak in Valgrind's libpthread; there's meant to be a
suppression for it (the leak is in our code, not yours) but it doesn't
seem to be working. In default.supp (should be wherever Valgrind is
installed), change 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
}
to this:
{
my_malloc/get_or_allocate_specifics_ptr/pthread_key_create(Leak)
Memcheck:Leak
fun:malloc
fun:my_malloc
fun:get_or_allocate_specifics_ptr
fun:pthread_key_create
}
which should get rid of it.
Does anyone else have this same problem, ie. this leak from David Hawkins'
program (posted on the valgrind-users list) isn't suppressed? I'll commit
it if so.
N
|