Hi Bruno!
> Le 4 oct. 2018 à 18:51, Bruno Haible a écrit :
>
> […]
>
> I would conclude that either times() or getrusage()+gettimeofday()
> provides the necessary functionality. Which one to choose? I think
> it's useful to compare the results on various platforms (regarding
> precision and
Tim Rühsen wrote:
The GNU standards [1] say so as well:
"Memory analysis tools such as valgrind can be useful, but don’t complicate
a program merely to avoid their false alarms. For example, if memory is used
until just before a process exits, don’t free it simply to silence such a
On 10/9/18 5:22 PM, Bruno Haible wrote:
>> I don't intend to do anything about the not serious ones.
>
> The GNU standards [1] say so as well:
> "Memory analysis tools such as valgrind can be useful, but don’t complicate
>a program merely to avoid their false alarms. For example, if memory
> I don't intend to do anything about the not serious ones.
The GNU standards [1] say so as well:
"Memory analysis tools such as valgrind can be useful, but don’t complicate
a program merely to avoid their false alarms. For example, if memory is used
until just before a process exits,
Hello Assaf
> It is a long tradition not to bother freeing memory in such cases
Yes. I remind the distinction between "not serious" and "serious"
memory leaks (as defined in https://en.wikipedia.org/wiki/Memory_leak ),
and I don't intend to do anything about the not serious ones.
Why?
1)
Hello gnulib,
'deltatau' recently reported 3 memory leaks detected in gnulib's test in
sed [1]. This was found using our recent ASAN build feature [2].
[1] https://bugs.gnu.org/32685
[2]
https://git.savannah.gnu.org/cgit/sed.git/commit/?id=0cc0ade4237b8db69f5253c3d933f9890b698f4d
It is a
