On Thu, 28 Jan 2016 06:36:32 -0800 (PST)
Arjun <tuarju...@gmail.com> wrote:
> Issue :
> 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
> git init
> git status
> Steps to reproduce:
> Just run git init or git status under valgrind using the default
> 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.
First, this list is to help Git newbies solve their problems with
*using* Git while your question is rather about its development--if
there really is a memory (de)allocation problem, it indicates a bug do
be fixed, right?
So you should rather direct this question to the main Git list where
its development is being discussed. Please read  for further
Second, a crucicial bit information is missing from your report: what
version of Git did you test? You know, the kind of information you're
presenting is only useful when it's being considered along with the
version of the code base it was produced against.
So please, when posting to the main Git list about your discoveries, be
sure to provide way more details about the version of Git being tested,
your system and the methodology you're using to produce the results.
Please refrain from mentioning you're a newbie -- there's nothing
bad about it, really. ;-)
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.