When running valgrind on grind using the memory check tool, memory leakage
is being identified.
During my initial tests, the following commands have produced memory
Steps to reproduce:
Just run git init or git status under valgrind using the default options.
Output of running valgrind on git status:
==19441== LEAK SUMMARY:
==19441== definitely lost: 2,187 bytes in 10 blocks
==19441== indirectly lost: 5 bytes in 1 blocks
==19441== possibly lost: 0 bytes in 0 blocks
==19441== still reachable: 126,455 bytes in 105 blocks
==19441== suppressed: 0 bytes in 0 blocks
Upon further inspection, using the --leak-check=full option, we find that
the final trace leads to
(below main) (libc-start.c:287)
Line 289 is the actual calling of the program from libc-start.c [ main
(argc, argv, __environ MAIN_AUXVEC_PARAM); ] and line 286 is [THREAD_SETMEM
(self, cleanup_jmp_buf, &unwind_buf); ] .
I really don't know if this is a very trivial bug or is natural. I admit
that I am not much of a developer or a security expert and so if I have
made some serious errors margining on stupidity, please correct me.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.