bcc icon indicating copy to clipboard operation
bcc copied to clipboard

Valgrind reports some memory leaks

Open GWRon opened this issue 5 years ago • 6 comments

I just compiled BCC with BCC and piped it through valgrind.

$ valgrind --leak-check=full ./bmk makeapp -g x64 -r -a /BlitzMaxNG.project/bcc-ng/bcc.bmx

[...]

==23348== LEAK SUMMARY:
==23348==    definitely lost: 58 bytes in 1 blocks
==23348==    indirectly lost: 0 bytes in 0 blocks
==23348==      possibly lost: 1,632 bytes in 6 blocks
==23348==    still reachable: 357,474 bytes in 4,445 blocks
==23348==         suppressed: 0 bytes in 0 blocks
==23348== Reachable blocks (those to which a pointer was found) are not shown.
==23348== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==23348== 
==23348== For counts of detected and suppressed errors, rerun with: -v
==23348== Use --track-origins=yes to see where uninitialised values come from
==23348== ERROR SUMMARY: 29959 errors from 72 contexts (suppressed: 0 from 0)

Something we have to worry about - or something not the fault of the generated C code by BCC?

GWRon avatar Jul 03 '19 22:07 GWRon