On Thu, Jun 26, 2008 at 23:33:04 +0200, Pierre Habouzit wrote: > On Thu, Jun 26, 2008 at 06:46:43PM +0000, Junio C Hamano wrote: > > The user would also need to worry about not freeing the original > > allocation pointer when something is realloc(3)ed, which means either > > finding the last realloc(3) of the object (that is logically the same, but > > just being extended) and mark the pointer as leaky() after that realloc, > > or unregister the original pointer from leaks before calling realloc and > > register what comes back. It will easily get messy. > > Hmm indeed, maybe it isn't such a good idea then. I don't think it's necessary either. Valgrind (unlike other leak detectors the poor windows folks are stuck with) is quite smart and will only report memory as leaked when there is no pointer to it. So it should not report any memory pointed to by index or any other static structure. Additionally since valgrind allows one to write rules to exclude uninteresting reports. So a good approach would be to just keep such exclusion file around in git with the known uninteresting cases. > > By the way, the series queued in your repository still has "s/pring/print/" > > typo in 4/7 and "argv not NULL terminated" comment in 6/7. > > I'll fix that and pushed again, without the leaky() series dependency > (I've put in a comment that I'm aware that it's a leak), and with the > two fixes you mention done. > > -- > ·O· Pierre Habouzit > ··O madcoder@xxxxxxxxxx > OOO http://www.madism.org -- Jan 'Bulb' Hudec <bulb@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
