Re: [Valgrind-users] Are these series bugs?

[John R. <jr...@bi...>]

> Are these series bugs?

I suppose you mean "serious bugs", that is, bugs that have
a large impact or must not be ignored.

> 
> My code is running fine.
> 
> Generally, how many memory leak is really bad?
> 
> 
> ==407== LEAK SUMMARY:
> ==407==    definitely lost: 3,752 bytes in 79 blocks
> ==407==    indirectly lost: 696 bytes in 87 blocks
> ==407==      possibly lost: 0 bytes in 0 blocks
> ==407==    still reachable: 1,040 bytes in 2 blocks
> ==407==         suppressed: 0 bytes in 0 blocks

Those leaks look relatively harmless, but ONLY IF:
that program runs quickly, and not too many times per day, and is not
a testcase for a long-running process (several hours or longer) or
for a process that will be run by many users simultaneously on the
same machine.  If the program takes a long time to run (minutes),
or is run more than five times per day, or is a simple example
of a a larger or longer-running process, or with many simultaneous
instantiations on the same machine, then such errors start to
become serious.


> ==407== ERROR SUMMARY: 10000076 errors from 679 contexts (suppressed: 11 from 9)

That's what I would worry about first: ten million errors (use of uninitialized
values) noticed at hundreds of locations in the code.  Probably you have
a few (2 or 3 or 4) _systematic_ errors.  Not only is there a problem,
but the problem occurs nearly every time, and will taint _everything_.
Such errors must be fixed.  Reduce the number of errors to fewer than ten.
There may be a programming concept which the author of the code
does not understand correctly.

--