Re: [Valgrind-users] Timer delete

[Paul F. <pj...@wa...>]

On 11/11/22 17:47, Domenico Panella wrote:
> Hi,
> 
> I am getting a memory leak in my program about timer_delete function.
> 
> According valgrind output,
> 
> It seems that the timer_delete function doesn't release the memory.
> 
> ==18483== HEAP SUMMARY:
> ==18483==     in use at exit: 272 bytes in 1 blocks
> ==18483==   total heap usage: 54 allocs, 53 frees, 9,354 bytes allocated
> ==18483==
> ==18483== 272 bytes in 1 blocks are possibly lost in loss record 1 of 1
> ==18483==    at 0x48475FF: calloc (vg_replace_malloc.c:1328)
> ==18483==    by 0x4012075: _dl_allocate_tls (in /lib64/ld-2.36.so)
> ==18483==    by 0x491EB49: pthread_create@@GLIBC_2.34 (in 
> /lib64/libc-2.36.so)
> ==18483==    by 0x492922D: __timer_start_helper_thread (in 
> /lib64/libc-2.36.so)
> ==18483==    by 0x4922E66: __pthread_once_slow (in /lib64/libc-2.36.so)
> ==18483==    by 0x4928D3A: timer_create@@GLIBC_2.34 (in 
> /lib64/libc-2.36.so)
> ==18483==    by 0x401711: main (main.c:224)
> ==18483==
> ==18483== LEAK SUMMARY:
> ==18483==    definitely lost: 0 bytes in 0 blocks
> ==18483==    indirectly lost: 0 bytes in 0 blocks
> ==18483==      possibly lost: 272 bytes in 1 blocks
> ==18483==    still reachable: 0 bytes in 0 blocks
> ==18483==         suppressed: 0 bytes in 0 blocks
> ==18483==
> ==18483== For lists of detected and suppressed errors, rerun with: -s
> ==18483== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
> 
> What do i wrong?

Which OS and CPU?

Is this repeatable?

It's possible that this is some memory that ought to be freed by the 
glibc freeres function.

Can you also post a small examp,e that reproduces the issue?

A+
Paul