Ok.
Thanks
Il 07/09/23 16:42, Floyd, Paul ha scritto:
On 07/09/2023 15:52, Domenico Panella wrote:
Hi,
I attached a valgrind log for my program.
I'd want an help to read it to understand if any error are there or not.
I don't think so but a confirm is much better.
Hi
There&#
Hi,
I attached a valgrind log for my program.
I'd want an help to read it to understand if any error are there or not.
I don't think so but a confirm is much better.
Thanks==17327== Memcheck, a memory error detector
==17327== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==17327=
[[snip horrible formatting]]
It looks so good.
Probably your email client messed up it.
Thanks so much for answer.
Good job,
Domenico
Il 12/11/22 01:46, John Reiser ha scritto:
On 11/11/22 13:23, Domenico Panella wrote:
Operating System: Slackware 15.0 (Current) Kernel Version: 5.19.17
(64
a scritto:
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
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
In data mercoledì 15 dicembre 2021 10:15:51 CET, David Chapman ha scritto:
Ok. Thanks
> On 12/15/2021 12:34 AM, Domenico Panella wrote:
> > Hi ,
> >
> > I'm getting this message when I run :
> >
> > valgrind --leak-check=full ./MyProg
> >
> >
Hi ,
I'm getting this message when I run :
valgrind --leak-check=full ./MyProg
==4189== HEAP SUMMARY:
==4189== in use at exit: 192 bytes in 12 blocks
==4189== total heap usage: 21 allocs, 9 frees, 3,513 bytes allocated
==4189==
==4189== LEAK SUMMARY:
==4189==definitely lost: 0 bytes i
