Re: identifying possible leak

> Hi,
>
> thanks for the reply. I am using version 3.14. As for the other leaks,
> they are all 'still reachable' and that was the only error reported by
> valgrind. Should take actions to avoid also the 'still reachable' leaks?
> Thnaks for the help I am new to valgrind and, as it is becoming quite
> helpful in my projects, I would like to correctly interpret its reports.
>
> Regards,
> Filippo
>
> On Mon, May 13, 2019, 11:49 PM John Reiser <[email protected]> wrote:
>
>> > =16595== 1,008 bytes in 3 blocks are possibly lost in loss record 155
>> of 1,524
>> > ==16595==    at 0x483AB65: calloc (vg_replace_malloc.c:752)
>> > ==16595==    by 0x4012A32: allocate_dtv (in /usr/lib/ld-2.29.so <
>> http://ld-2.29.so>)
>> > ==16595==    by 0x40133E1: _dl_allocate_tls (in /usr/lib/ld-2.29.so <
>> http://ld-2.29.so>)
>>
>> Anything allocated by a routine which is part of the dynamic linker (such
>> as _dl_allocate_tls
>> in /usr/lib/ld-*.so) should be ignored.  The dynamic linker is well-known
>> to leak,
>> and some of those leaks essentially cannot be eliminated.  In any case,
>> you cannot do anything
>> about those leaks.  Besides, this leak is less than 340 bytes on average
>> (1008 / 3),
>> and there are either 154 or (1524 - 154) leaks which are more important
>> (larger).
>>
>> [Next time, please state the version of valgrind that you ran.]
>>
>>
>> _______________________________________________
>> Valgrind-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>>
>

_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users